Symptoms
Boot2docker VM fails to boot after multiple "Warning: Connection timeout. Retrying..." messages.
Cause
Host machine does not have virtualization support (VT-x) or has it disabled.
Confirm by attaching to the VM console.
Solution
Enable VT-x in BIOS.
Machines without VT-x support won't work with Drude / boot2docker-vagrant / 64bit VirtualBox VMs.
Symptoms
- "Layer already being pulled by another client"
- Permission Denied while mounting NFS shared folders
- Stale NFS handle error
Cause
VirtualBox ships with a preconfigured DHCP server which gets in the way, sometimes in very unobvious cases.
Sometimes the cause may not be the DHCP server, but a corrupt VM network adapter.
Solution
-
Note the Host-only Adapter name used by the VM.
-
Open VirtualBox Preferences > Network > Host-only Netowrks and kill that adapter.
-
Restart the VM.
