This repository has been archived by the owner on Sep 18, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 13
Issues, Fixes and Feature Requests #10
Comments
You could try this. https://github.com/daxgames/packer-post-processor-vsphere-ova/tree/ovftool_import I have a pull request open here but @rubbish has had issues getting it working. I would love for someone else to try it because I cannot test it at this point I do not currently have access to vSphere. |
@daxgames I am testing out Ansible with ESXi 5.5 now, will try that soon and share my result. Thanks ! |
Thanks. I hope it works for you. |
@vikas027 Glad to hear it. |
Open
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I have got this to make it work finally with some issues (may be bugs).
ENVIRONMENT
ISSUES and FIXES
I guess there are two main reasons for the failure
Other (32-bit)
which is neither Linux nor WindowsHowever, I fixed these issues using this script. Thanks to shell-local post-processor introduced in packer v0.9.0.
But still my build gave the same error as above. Somehow, post-processor keeps waiting for VM Tools to be recognized which are not installed in my Virtualbox VMs. And AFAIK, VMware Tools do not get installed in a VirtualBox VM. So, in order to make your post-processor work, I create below script while provisioning VM and called it through
rc.local
(which gets invoked when ESXi powers on the VM.Finally, I was able to make everything work. I can sleep happily now :)
FEATURE REQUESTS
It would be great (may be a toggle) for these options
-vm
at the end)"keep_input_artifact": false
has no effect as of nowThe text was updated successfully, but these errors were encountered: