We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When creating an os+db image, Packer throws an error: Error updating template: ide1 - cloud-init drive is already attached at 'ide0'.
The reason is that Packer did not remove the old cloud-init and trying to insert a new one.
The removal occurs in the code: https://github.com/hashicorp/packer-plugin-proxmox/blob/main/builder/proxmox/common/step_remove_cloud_init_drive.go#L56
If you create cloud-init on local disks, the file name will also include the disk format:
my $scfg = PVE::Storage::storage_config($storecfg, $storeid); my $name = "vm-$vmid-cloudinit"; my $fmt = undef; if ($scfg->{path}) { $fmt = $disk->{format} // "qcow2"; $name .= ".$fmt"; } else { $fmt = $disk->{format} // "raw"; }
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
When creating an os+db image, Packer throws an error: Error updating template: ide1 - cloud-init drive is already attached at 'ide0'.
The reason is that Packer did not remove the old cloud-init and trying to insert a new one.
The removal occurs in the code: https://github.com/hashicorp/packer-plugin-proxmox/blob/main/builder/proxmox/common/step_remove_cloud_init_drive.go#L56
If you create cloud-init on local disks, the file name will also include the disk format:
The text was updated successfully, but these errors were encountered: