Hi Alvaro, First, thanks for reading and commenting!
I'm pretty sure it should work, but then again, it isn't right now :-) Only a single match on a web search for "run VirtualBox within container on Mac" is unanswered. https://stackoverflow.com/questions/47095233/run-virtualbox-inside-a-docker-container-on-macos I'm hoping there are those out there that have done, or tried to do, the same thing. This error is very specific, yet still vague in meaning. Web search also has no hits on the source file or line number. To answer your specific questions, yes, VMware runs within the Ubuntu container on a Mac (which uses a xhyve VM). I hoped to be clear that it was a VMware VIX issue, ... looking for the magic recipe to do this workflow. This will be useful to those running Mac+Docker+Ubuntu+Packer+VMware. Thanks On Monday, September 9, 2019 at 1:13:11 PM UTC-5, Alvaro Miranda Aguilera wrote: > > hello > > just to make sure i understand. > > you are truing to run vmware inside a docker container? > i assume the container run in some sort of vm too. > > probably wont work as 64 bit require access to hw virtualization. > > vmware requires access to hw virtualization, so not a packer issue at this > moment. > > you can try to run vmware without packer and you should have some sort of > error. > > > alvaro > > On Mon, Sep 9, 2019 at 6:46 PM m40 <[email protected] <javascript:>> > wrote: > >> *Background*: >> Host is a Mac, built an Ubuntu 16.04 container, performed these steps >> within the container: >> cd /var/images >> bash VMware-Player-14.1.7-12989993.x86_64.bundle >> bash VMware-VIX-1.17.0-6661328.x86_64.bundle >> unzip packer_1.4.3_linux_amd64.zip >> export PATH=/var/images:$PATH >> cp netmap.conf /etc/vmware/netmap.conf >> >> *References*: >> https://www.packer.io/docs/builders/vmware-iso.html >> >> https://elatov.github.io/2018/11/use-packer-with-vmware-player-to-build-an-ova/. >> >> <-- very good reference >> >> *Environment* >> root@cae0e9a7acb4:/var/images# packer -v >> 1.4.3 >> >> root@cae0e9a7acb4:/var/images# vmware-installer -l >> Product Name Product Version >> ==================== ==================== >> vmware-player 14.1.7.12989993 >> vmware-vix 1.17.0.6661328 >> >> root@cae0e9a7acb4:/var/images# uname -a >> Linux cae0e9a7acb4 4.9.184-linuxkit #1 SMP Tue Jul 2 22:58:16 UTC 2019 >> x86_64 x86_64 x86_64 GNU/Linux >> >> root@cae0e9a7acb4:/var/images# cat /etc/lsb-release >> DISTRIB_ID=Ubuntu >> DISTRIB_RELEASE=16.04 >> DISTRIB_CODENAME=xenial >> DISTRIB_DESCRIPTION="Ubuntu 16.04.6 LTS" >> >> root@cae0e9a7acb4:/var/images# cat netmap.conf >> network0.name = "Bridged" >> network0.device = "vmnet0" >> network1.name = "HostOnly" >> network1.device = "vmnet1" >> network2.name = "VMNet2" >> network2.device = "vmnet2" >> network8.name = "NAT" >> network8.device = "vmnet8" >> >> root@cae0e9a7acb4:/var/images# cat app.json >> { >> "builders": [ >> { >> "type": "vmware-iso", >> "iso_url": >> "file:///var/images/ubuntu-16.04.6-server-amd64.iso", >> "iso_checksum": "ac8a79a86a905ebdc3ef3f5dd16b7360", >> "iso_checksum_type": "md5", >> "ssh_username": "root", >> "ssh_password": "secret", >> "disk_size": "4096", >> "headless": true, >> "shutdown_command": "shutdown -P now", >> "boot_command": >> [ >> "<enter><wait>" >> ] >> } >> ] >> } >> >> root@cae0e9a7acb4:/var/images# ./packer build app.json >> >> vmware-iso output will be in this color. >> >> >> ==> vmware-iso: Retrieving ISO >> >> ==> vmware-iso: Trying file:///var/images/ubuntu-16.04.6-server-amd64.iso >> >> ==> vmware-iso: Trying >> file:///var/images/ubuntu-16.04.6-server-amd64.iso?checksum=md5%3Aac8a79a86a905ebdc3ef3f5dd16b7360 >> >> ==> vmware-iso: >> file:///var/images/ubuntu-16.04.6-server-amd64.iso?checksum=md5%3Aac8a79a86a905ebdc3ef3f5dd16b7360 >> >> => /var/images/packer_cache/03fbc619c10aa1efeebbc88e7810e46599c8c225.iso >> >> ==> vmware-iso: Creating required virtual machine disks >> >> ==> vmware-iso: Building and writing VMX file >> >> ==> vmware-iso: Starting virtual machine... >> >> vmware-iso: The VM will be run headless, without a GUI. If you want to >> >> vmware-iso: view the screen of the VM, connect via VNC with the >> password "LXg3kFdy" to >> >> vmware-iso: vnc://127.0.0.1:5929 >> >> ==> vmware-iso: Error starting VM: VMware error: VERIFY >> bora/lib/misc/hostinfoPosix.c:1771 >> >> ==> vmware-iso: >> >> ==> vmware-iso: VMware Player Error: >> >> ==> vmware-iso: VMware Player unrecoverable error: (vthread-2) >> >> ==> vmware-iso: VERIFY bora/lib/misc/hostinfoPosix.c:1771 >> >> ==> vmware-iso: A log file is available in >> "/tmp/vmware-root/vmware-vix-1217.log". >> >> ==> vmware-iso: You can request support. >> >> ==> vmware-iso: >> >> ==> vmware-iso: To collect data to submit to VMware technical support, >> run "vm-support". >> >> ==> vmware-iso: We will respond on the basis of your support entitlement. >> >> ==> vmware-iso: Waiting 4.297839814s to give VMware time to clean up... >> >> ==> vmware-iso: Deleting output directory... >> >> Build 'vmware-iso' errored: Error starting VM: VMware error: VERIFY >> bora/lib/misc/hostinfoPosix.c:1771 >> >> >> VMware Player Error: >> >> VMware Player unrecoverable error: (vthread-2) >> >> VERIFY bora/lib/misc/hostinfoPosix.c:1771 >> >> A log file is available in "/tmp/vmware-root/vmware-vix-1217.log". >> >> You can request support. >> >> >> To collect data to submit to VMware technical support, run "vm-support". >> >> We will respond on the basis of your support entitlement. >> >> >> ==> Some builds didn't complete successfully and had errors: >> >> --> vmware-iso: Error starting VM: VMware error: VERIFY >> bora/lib/misc/hostinfoPosix.c:1771 >> >> >> VMware Player Error: >> >> VMware Player unrecoverable error: (vthread-2) >> >> VERIFY bora/lib/misc/hostinfoPosix.c:1771 >> >> A log file is available in "/tmp/vmware-root/vmware-vix-1217.log". >> >> You can request support. >> >> >> To collect data to submit to VMware technical support, run "vm-support". >> >> We will respond on the basis of your support entitlement. >> >> >> ==> Builds finished but no artifacts were created. >> >> The output from `PACKER_LOG=1 ./packer build app.json` pertinent to the >> failure is: >> >> ==> vmware-iso: Starting virtual machine... >> vmware-iso: The VM will be run headless, without a GUI. If you want to >> vmware-iso: view the screen of the VM, connect via VNC with the >> password "0GSEJ2ZT" to >> vmware-iso: vnc://127.0.0.1:5947 >> 2019/09/09 16:40:05 packer: 2019/09/09 16:40:05 Executing: /usr/bin/vmrun >> -T player start output-vmware-iso/packer-vmware-iso.vmx nogui >> 2019/09/09 16:40:06 packer: 2019/09/09 16:40:06 stdout: Error: Unknown >> error >> 2019/09/09 16:40:06 packer: 2019/09/09 16:40:06 stderr: VERIFY >> bora/lib/misc/hostinfoPosix.c:1771 >> 2019/09/09 16:40:06 packer: >> 2019/09/09 16:40:06 packer: VMware Player Error: >> 2019/09/09 16:40:06 packer: VMware Player unrecoverable error: (vthread-2) >> 2019/09/09 16:40:06 packer: VERIFY bora/lib/misc/hostinfoPosix.c:1771 >> 2019/09/09 16:40:06 packer: A log file is available in >> "/tmp/vmware-root/vmware-vix-1286.log". >> 2019/09/09 16:40:06 packer: You can request support. >> 2019/09/09 16:40:06 packer: >> 2019/09/09 16:40:06 packer: To collect data to submit to VMware technical >> support, run "vm-support". >> 2019/09/09 16:40:06 packer: We will respond on the basis of your support >> entitlement. >> ==> vmware-iso: >> ==> vmware-iso: VMware Player Error: >> ==> vmware-iso: VMware Player unrecoverable error: (vthread-2) >> ==> vmware-iso: VERIFY bora/lib/misc/hostinfoPosix.c:1771 >> ==> vmware-iso: A log file is available in >> "/tmp/vmware-root/vmware-vix-1286.log". >> ==> vmware-iso: You can request support. >> ==> vmware-iso: >> ==> vmware-iso: To collect data to submit to VMware technical support, >> run "vm-support". >> ==> vmware-iso: We will respond on the basis of your support entitlement. >> >> I understand that this is a VIX/vmrun issue. I suspect something might >> not be configured properly in that area to work with Docker+Ubuntu+Packer. >> Any recommendations/suggestions will be gratefully received! >> >> Thanks! >> >> >> -- >> This mailing list is governed under the HashiCorp Community Guidelines - >> https://www.hashicorp.com/community-guidelines.html. Behavior in >> violation of those guidelines may result in your removal from this mailing >> list. >> >> GitHub Issues: https://github.com/mitchellh/packer/issues >> IRC: #packer-tool on Freenode >> --- >> You received this message because you are subscribed to the Google Groups >> "Packer" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/packer-tool/b1f8f12e-7694-4131-942b-fc42814bb2c4%40googlegroups.com >> >> <https://groups.google.com/d/msgid/packer-tool/b1f8f12e-7694-4131-942b-fc42814bb2c4%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> > > > -- > Alvaro > > -- This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list. GitHub Issues: https://github.com/mitchellh/packer/issues IRC: #packer-tool on Freenode --- You received this message because you are subscribed to the Google Groups "Packer" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/packer-tool/7a36676b-677f-43dd-9903-f4c69a370730%40googlegroups.com.
