New issue
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
Add remove_cdrom to vmware-iso #10704
Comments
The root of this, may actually be a bug with cd_files. I will look at this some more, and maybe open a bug issue. The drive does not get removed from the VMX like the floppy does. |
Annoyingly, if you try to export the However, in your specific situation, you can probably work around it temporarily by adding something like I haven't tested it, but the fix for this should be as simple as appending the device to the packer/builder/vmware/common/step_configure_vmx.go Lines 68 to 97 in 4bbeec4
|
I think I tried that! For now I'm using grep to remove it. Grep can't overwrite a file, so i just write it to tmp.
|
This issue has been migrated to hashicorp/packer-plugin-vmware#33 due to the Packer Plugin split. Please follow the new issue for updates. |
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. |
Community Note
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request.
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request.
If you are interested in working on this issue or have submitted a pull request, please leave a comment.
Description
I would like to be able to use remove_cdrom with the vmware-iso provider. I am adding a disk using cd_files with vmware-iso, then I am use vmware-vmx to import the vmx, do some more config and convert to ova. However, the conversion fails because the temporary ISO no longer exists. I would like to cleanup the CD drive in the vmware-iso run. I may be able to fix this with ovftool_options, but have not gotten that to work yet.
Use Case(s)
Potential configuration
Potential References
The text was updated successfully, but these errors were encountered: