Packer v1.2.1
Windows 2012 R2
Unknown Key: disk_additional_size
We are trying to add additional disk in Azure and getting error on disk_additional_size
"builders": [{
"type": "azure-arm",
"client_id": "{{user `client_id`}}",
"client_secret": "{{user `client_secret`}}",
"resource_group_name": "{{user `resource_group`}}",
"storage_account": "{{user `storage_account`}}",
"subscription_id": "{{user `subscription_id`}}",
"tenant_id": "{{user `tenant_id`}}",
"capture_container_name": "images",
"capture_name_prefix": "packer",
"ssh_username": "{{user `ssh_user`}}",
"ssh_password": "{{user `ssh_pass`}}",
"os_type": "Linux",
"image_publisher": "OpenLogic",
"image_offer": "CentOS",
"image_sku": "7.4",
"image_version": "latest",
"disk_additional_size": [
100
],
"ssh_pty": "true",
"location": "West Central US",
"vm_size": "Standard_DS2_v2"
}]
can you run with PACKER_LOG=1
and paste the output please
Attached PACKER_LOG=1
I'm afraid I'm unable to reproduce this error. Does the following json file validate correctly (packer validate packer.json
)?
{
"builders": [
{
"capture_container_name": "images",
"capture_name_prefix": "packer",
"client_id": "foo",
"client_secret": "foo",
"disk_additional_size": [
100
],
"image_offer": "CentOS",
"image_publisher": "OpenLogic",
"image_sku": "7.4",
"image_version": "latest",
"location": "West Central US",
"os_type": "Linux",
"resource_group_name": "foo",
"ssh_password": "foo",
"ssh_pty": "true",
"ssh_username": "foo",
"storage_account": "foo",
"subscription_id": "foo",
"tenant_id": "foo",
"type": "azure-arm",
"vm_size": "Standard_DS2_v2"
}
]
}
Packer validate also returns the same unknown key (* unknown configuration key: "disk_additional_size"
)
I followed the Azure Builder Documentation
Please upgrade to the latest version of Packer, and try again. The latest version is 1.2.2.
Yes, After upgrade to latest version it worked!
I'm going to lock this issue because it has been closed for _30 days_ โณ. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
Most helpful comment
Yes, After upgrade to latest version it worked!