title: OSX boot2docker hangs on "Waiting for VM and Docker daemon to start …"
body: <p>I've installed <code>boot2docker</code> on <code>OSX 10.8.5</code> and it seems that the installation went fine, but when I try to launch <code>boot2docker</code> I get the following, which hangs indefinitely:</p>
  
  <pre><code>$ /usr/local/bin/boot2docker up 
  Waiting for VM and Docker daemon to start...
  ..........................................................................oooooooooooooooooooooooooooooo
  </code></pre>
  
  <p>What steps should I take to debug this? I haven't been able to find any information on this particular issue.</p>
  
  <pre><code>$ boot2docker version
  Boot2Docker-cli version: v1.4.1
  Git commit: 43241cb
  
  $ docker version
  Client version: 1.4.1
  Client API version: 1.16
  Go version (client): go1.3.3
  Git commit (client): 5bc2ff8
  OS/Arch (client): darwin/amd64
  
  $ boot2docker -v up
  Boot2Docker-cli version: v1.4.1
  Git commit: 43241cb
  2014/12/23 00:19:25 executing: VBoxManage showvminfo boot2docker-vm --machinereadable
  2014/12/23 00:19:25 executing: VBoxManage showvminfo boot2docker-vm --machinereadable
  2014/12/23 00:19:25 executing: VBoxManage showvminfo boot2docker-vm --machinereadable
  Waiting for VM and Docker daemon to start...
  .Connecting to tcp://localhost:2022 (attempt #0).Connecting to tcp://localhost:2022 (attempt #0).Connecting to tcp://localhost:2022 (attempt #0).Connecting to tcp://localhost:2022 (attempt #0).Connecting to tcp://localhost:2022 (attempt #0).^C
  </code></pre>
  
  <p><hr></p>
  
  <p>In my <code>~/.bash_profile</code> file:</p>
  
  <pre><code>export DOCKER_HOST=tcp://192.168.59.103:2376
  export DOCKER_CERT_PATH=/Users/Me/.boot2docker/certs/boot2docker-vm
  export DOCKER_TLS_VERIFY=1
  </code></pre>
  
  <p><hr></p>
  
  <p>When I open <code>VirtualBox</code>, this what I see:</p>
  
  <p><img src="https://i.stack.imgur.com/edVif.png" alt="enter image description here"></p>
  
  <p><hr>
  I've tried <code>powering off</code> and <code>removing</code> the <code>boot2docker-vm</code> using the <code>Virtual Box</code> GUI, and I get the following when I run <code>boot2docker</code> again:</p>
  
  <pre><code>$ /usr/local/bin/boot2docker init 
  error in run: Failed to initialize machine "boot2docker-vm": exit status 2
  </code></pre>
  
  <p>And then:</p>
  
  <pre><code>$ /usr/local/bin/boot2docker up 
  Waiting for VM and Docker daemon to start...
  ...............................................................…..
  </code></pre>
  
  <p>Which hangs endlessly.</p>
  
  <p><hr></p>
  
  <p><strong>Additionally</strong></p>
  
  <pre><code>$ docker ps
  FATA[0000] Couldn't read ca cert /Users/Me/.boot2docker/certs/boot2docker-vm/ca.pem: open /Users/Me/.boot2docker/certs/boot2docker-vm/ca.pem: no such file or directory
  </code></pre>
  
  <p>And:</p>
  
  <pre><code>$ sudo docker ps
  FATA[0000] Get http:///var/run/docker.sock/v1.16/containers/json: dial unix /var/run/docker.sock: no such file or directory. Are you trying to connect to a TLS-enabled daemon without TLS?
  </code></pre>
  
  <p><hr></p>
  
  <p>Following Sven's advice below deleted the <code>boot2docker-vm</code> again and run <code>init</code> in verbose mode:</p>
  
  <pre><code>    $ boot2docker -v init
  Boot2Docker-cli version: v1.4.1
  Git commit: 43241cb
  2014/12/23 01:53:02 executing: VBoxManage showvminfo boot2docker-vm --machinereadable
  2014/12/23 01:53:02 executing: VBoxManage showvminfo boot2docker-vm --machinereadable
  2014/12/23 01:53:03 executing: VBoxManage list vms
  2014/12/23 01:53:03 executing: VBoxManage createvm --name boot2docker-vm --register
  Virtual machine 'boot2docker-vm' is created and registered.
  UUID: eca00a0a-6d68-45f3-acd1-ccc4dd1bcec9
  Settings file: '/Users/Me/VirtualBox VMs/boot2docker-vm/boot2docker-vm.vbox'
  2014/12/23 01:53:03 executing: VBoxManage showvminfo boot2docker-vm --machinereadable
  2014/12/23 01:53:03 executing: VBoxManage setextradata boot2docker-vm VBoxInternal/CPUM/EnableHVP 1
  2014/12/23 01:53:03 executing: VBoxManage modifyvm boot2docker-vm --firmware bios --bioslogofadein off --bioslogofadeout off --bioslogodisplaytime 0 --biosbootmenu disabled --natdnshostresolver1 off --natdnsproxy1 off --ostype Linux26_64 --cpus 8 --memory 2048 --vram 8 --acpi on --ioapic on --rtcuseutc on --cpuhotplug off --pae on --longmode on --synthcpu off --hpet on --hwvirtex on --triplefaultreset off --nestedpaging on --largepages on --vtxvpid on --vtxux off --accelerate3d off --uart1 0x3F8 4 --uartmode1 server /Users/AJB/.boot2docker/boot2docker-vm.sock --boot1 dvd
  2014/12/23 01:53:03 executing: VBoxManage showvminfo boot2docker-vm --machinereadable
  2014/12/23 01:53:03 executing: VBoxManage modifyvm boot2docker-vm --nic1 nat --nictype1 virtio --cableconnected1 on
  2014/12/23 01:53:03 executing: VBoxManage controlvm boot2docker-vm natpf1 ssh,tcp,127.0.0.1,2022,,22
  2014/12/23 01:53:03 executing: VBoxManage list hostonlyifs
  2014/12/23 01:53:03 executing: VBoxManage list dhcpservers
  2014/12/23 01:53:03 executing: VBoxManage hostonlyif create
  0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
  2014/12/23 01:53:03 executing: VBoxManage hostonlyif ipconfig dyld: DYLD_ environment variables being ignored because main executable (/Applications/VirtualBox.app/Contents/MacOS/VBoxNetAdp --ip 192.168.59.3 --netmask 255.255.255.0
  VBoxManage: error: The host network interface with the given name could not be found
  VBoxManage: error: Details: code NS_ERROR_INVALID_ARG (0x80070057), component Host, interface IHost, callee nsISupports
  VBoxManage: error: Context: "FindHostNetworkInterfaceByName(name.raw(), hif.asOutParam())" at line 218 of file VBoxManageHostonly.cpp
  VBoxManage: error: Could not find interface 'dyld: DYLD_ environment variables being ignored because main executable (/Applications/VirtualBox.app/Contents/MacOS/VBoxNetAdp'
  error in run: Failed to initialize machine "boot2docker-vm": exit status 2
  </code></pre>
  
  <p><hr></p>
  
  <p>Thanks in advance for any help.</p>