driver vmwarefusion: Error creating machine: IP not found for MAC ... in DHCP leases

[DieterRogiest]

On OS X high sierra and on the new mojave (with virtualbox and parallels uninstalled) I am not able to create with docker-machine a boot2docker (v18.09.0-beta3) vm with driver vmwarefusion (or even driver vmware) without these errors:

Macs-MacBook-Pro:~ mac$ docker-machine -D create --vmwarefusion-boot2docker-url=/Users/mac/.docker/machine/cache/boot2docker.iso --driver=vmwarefusion vmware-dev
Docker Machine Version:  0.15.0, build b48dc28d
...
(vmware-dev) DBG | executing: /Applications/VMware Fusion.app/Contents/Public/vmrun start /Users/mac/.docker/machine/machines/vmware-dev/vmware-dev.vmx nogui
(vmware-dev) Waiting for VM to come online...
(vmware-dev) DBG | executing: /Applications/VMware Fusion.app/Contents/Public/vmrun list
(vmware-dev) DBG | MAC address in VMX: 00:0c:29:47:b5:db
(vmware-dev) DBG | Trying to find IP address in configuration file: /Library/Preferences/VMware Fusion/vmnet1/dhcpd.conf
(vmware-dev) DBG | Following IPs found map[00:50:56:c0:00:01:172.16.127.1]
(vmware-dev) DBG | Trying to find IP address in configuration file: /Library/Preferences/VMware Fusion/vmnet8/dhcpd.conf
(vmware-dev) DBG | Following IPs found map[00:50:56:c0:00:08:192.168.173.1]
(vmware-dev) DBG | Trying to find IP address in leases file: /var/db/vmware/vmnet-dhcpd-vmnet1.leases
(vmware-dev) DBG | Trying to find IP address in leases file: /var/db/vmware/vmnet-dhcpd-vmnet8.leases
(vmware-dev) DBG | Not there yet 1/60, error: IP not found for MAC 00:0c:29:47:b5:db in DHCP leases
...
(vmware-dev) DBG | Not there yet 60/60, error: IP not found for MAC 00:0c:29:47:b5:db in DHCP leases
Error creating machine: Error in driver during machine creation: Machine didn't return an IP after 120 seconds, aborting

Macs-MacBook-Pro:cache mac$ docker-machine ls
NAME          ACTIVE   DRIVER         STATE     URL   SWARM   DOCKER    ERRORS
vmware-dev    *        vmwarefusion   Running                 Unknown   IP not found for MAC 00:0c:29:47:b5:db in DHCP leases

On machine-drivers/docker-machine-driver-xhyve#9 I found :
machine-drivers/docker-machine-driver-xhyve#9 (comment) (and the following comments).
I tried to to forcefully start bootpd.plist but that didn't work.
For some reason docker-machine on my macbook with driver vmwarefusion does not get or does not request an IP address for the new vm.
In the VM I am thus not able to access the internet.
Normal VM's like CentOS are able to access the internet.
The boot2docker VM's I created with virtualbox driver could access internet but virtualbox VM's do not have CPU acceleration.

[DieterRogiest]

well, I got internet access working in my vmwarefusion boot2docker vm (see below) but after that I had to give up as my "docker run" command got killed before it could finish downloading butomo1989/docker-android-x86-8.1 and I don't know why.
In The boot2docker VM created with virtualbox I coud run the "docker run ... butomo1989/docker-android-x86-8.1" command and I was able from to access the vnc url in osx that showed me an empty openbox screen without an android emulator running because virtualbox has no support for nested virtualization (CPU acceleration).

So googling "vmware fusion dhcp not working" I found https://communities.vmware.com/thread/578090?start=15&tstart=0 :

No internet in guest, not using NAT or Bridged, despite trying all the manual suggestions in this thread.
VMWare support removed my only network adapter:
Shut down guest, Settings > Network Adapter > Advanced options > Remove Network Adapter.
And added a new adapter, Settings > Add Device > Network Adapter. Changed from NAT to Bridged. Start guest

So I did that:
I copied from existing network adapter the MAC address, I unticked the "Connnect Network Adapter", and added a new device Network Adapter with that MAC address (so I did not generate one)
I set it to Internet Sharing:Share with my Mac (NAT),
booted the vm,
and in it ifconfig showed now an eth0 with ipv4 address.

And "curl http://www.google.com" then worked!
And /var/db/vmware/vmnet-dhcpd-vmnet8.leases finally showed an entry for this vm.

Macs-MacBook-Pro:cache mac$ docker-machine ls
NAME          ACTIVE   DRIVER         STATE     URL   SWARM   DOCKER    ERRORS
vmware-dev    *        vmwarefusion   Running                 Unknown   couldn't find MAC address in VMX file /Users/mac/.docker/machine/machines/vmware-dev/vmware-dev.vmx

I could not figure out that error "couldn't find MAC address in VMX".

[kaosagnt]

See #1315
as it is probably related.

Using the vmware driver fixed my issues.

https://github.com/machine-drivers/docker-machine-driver-vmware

go get -u github.com/machine-drivers/docker-machine-driver-vmware

[DieterRogiest]

nope, I had also tried the vmware driver instead of the vmwarefusion (as I had written before)

[MartinSGill]

I'm encountering the same issue with VMWare Workstation Pro 15.

If I log into the VM directly I can see that eth0 doesn't exist.

When I instead tried to use the boot2docker.iso in packer, I discovered that I need to set "ethernet0.virtualDev": "e1000" for the eth0 to show up.

This suggests to me that boot2docker is not able to recognise the network card that vmxnet3 emulates. But it does still recognise the more primitive software base NIC emulator.

[MartinSGill]

MIght be the same issue as #1345

[tianon]

Doh, good catch! I think I've found the source of the issue (and will be making a PR shortly):

$ docker run --rm boot2docker/boot2docker grep -i vmxnet /usr/src/linux/.config
# CONFIG_VMXNET3 is not set

[tianon]

Can someone here do a build of #1350 and verify that it fixes the issue? (I don't have a VMware install to test this on at the moment.)

[StefanScherer]

I've built the boot2docker.iso
https://github.com/StefanScherer/boot2docker/releases/download/v18.09.0-vmxnet3/boot2docker.iso
SHA256 checksum is f48a4ef3641123f26308444b22bea70ac438d714b52dc1fd1fa025f949786412.
If someone wants to try it. I've added my first findings in #1350 and will try it with an older VMware Fusion version tomorrow.

[kaosagnt]

I diffed the generated Kernel config with my working one. This stands out for VMWare folk.

-# CONFIG_VMWARE_VMCI is not set
+CONFIG_VMWARE_VMCI=m

+CONFIG_VMWARE_BALLOON=m

-# CONFIG_OPENVSWITCH is not set
-# CONFIG_VSOCKETS is not set
-# CONFIG_NETLINK_DIAG is not set
-# CONFIG_MPLS is not set
+CONFIG_OPENVSWITCH=m
+CONFIG_OPENVSWITCH_VXLAN=m
+CONFIG_VSOCKETS=m
+CONFIG_VMWARE_VMCI_VSOCKETS=m
+CONFIG_VIRTIO_VSOCKETS=m
+CONFIG_VIRTIO_VSOCKETS_COMMON=m
+CONFIG_HYPERV_VSOCKETS=m

There is probably others I have missed. I'll keep digging.

[tekook]

@StefanScherer

I've built the boot2docker.iso
https://github.com/StefanScherer/boot2docker/releases/download/v18.09.0-vmxnet3/boot2docker.iso
SHA256 checksum is f48a4ef3641123f26308444b22bea70ac438d714b52dc1fd1fa025f949786412.
If someone wants to try it. I've added my first findings in #1350 and will try it with an older VMware Fusion version tomorrow.

can confirm this iso is working fine with vmwareworkstation-driver.
VMware Workstion Pro 15