create hangs forever on OSX

[kopiczko]

Hey,

OSX: 10.10.5

~/org ❯❯❯ docker-machine --version
docker-machine version 0.4.1 (e2c88d6)

~/org ❯❯❯ VBoxManage --version
5.0.0r101573

I was trying to upgrade from boot2docker to docker-machine. I had removed boot2docker and docker (installed with brew), and removed ~/.docker directory.
When I try to create new default machine:

~/org ❯❯❯ docker-machine create  --driver virtualbox default
Creating CA: /Users/pawel/.docker/machine/certs/ca.pem
Creating client certificate: /Users/pawel/.docker/machine/certs/cert.pem
Image cache does not exist, creating it at /Users/pawel/.docker/machine/cache...
No default boot2docker iso found locally, downloading the latest release...
Downloading https://github.com/boot2docker/boot2docker/releases/download/v1.8.1/boot2docker.iso to /Users/pawel/.docker/machine/cache/boot2docker.iso...
Creating VirtualBox VM...
Creating SSH key...
Starting VirtualBox VM...
Starting VM...

docker-machine ls output (asks me for password):

~/org ❯❯❯ docker-machine ls
Password:
Password:NAME      ACTIVE   DRIVER       STATE     URL   SWARM
default            virtualbox   Timeout

I also see 'Password:' prompt in Docker Quickstart Terminal:

[rayward]

+1 same issues exactly.

[ehazlett]

Hmm @nathanleclaire do you see the same behavior with 1.8.1? It looks like the SSH keys are not setup properly.

[nathanleclaire]

I haven't been seeing issues like this myself, but it's been a while since I've booted up the Quickstart terminal. I'll give it a whirl soon.

[xi2008wang]

is virtualbox 5.0.0 bug!
upgrade virtualbox 5.0.4 !
http://download.virtualbox.org/virtualbox/5.0.4/VirtualBox-5.0.4-102546-OSX.dmg

[webframp]

How can I confirm if it's a vbox bug?
I'm seeing the same thing with the latest VirtualBox:

~ ❯❯❯ VBoxManage --version
5.0.4r102546
~ ❯❯❯ docker-machine --version
docker-machine version 0.4.1 (HEAD)
~ ❯❯❯ docker --version
Docker version 1.8.2, build 0a8c2e3

[alrayyes]

+1

➜  ~  docker-machine ls

NAME      ACTIVE   DRIVER       STATE     URL   SWARM
default            virtualbox   Timeout

[nathanleclaire]

@alrayyes can you please Gist the output of running docker-machine --debug ls?

[alrayyes]

Here you go. Vbox.log also seems to be showing an error:

00:00:40.874355 VMMDev: Guest Log: 00:00:00.017302 vminfo   rtldrNativeLoad: dlopen('libdbus-1.so.3', RTLD_NOW | RTLD_LOCAL) failed: libdbus-1.so.3: cannot open shared object file: No such file or directory
00:00:40.874500 VMMDev: Guest Log: 00:00:00.017458 vminfo   Error: Unable to connect to system D-Bus (1/3): D-Bus not installed
00:00:41.249068 NAT: IPv6 not supported
00:00:45.877512 VMMDev: Guest Log: 00:00:05.022513 vminfo   Error: Unable to connect to system D-Bus (2/3): D-Bus not installed
00:00:50.882160 VMMDev: Guest Log: 00:00:10.027818 vminfo   Error: Unable to connect to system D-Bus (3/3): D-Bus not installed

Could the two issues be related?

[buddhafinger]

I was experiencing similar issues:

My setup:

• OS X 10.10.5
• VirtualBox 5.0.4
• Docker Toolbox 1.8.2c

Problems experienced:

• Quickstart terminal launches default instance and then prompts for password.
• Same D-Bus not installed errors in the log.
• Unable to successfully recreate the default instance using Kitematic (failed as unable to connect to instance)

Resolution:

• Deleted the default docker machine and all associated files.
• Deleted 'Host only Networks' in Virtualbox - Preferences - Network - Host Only Network.
• Launch Kitematic and let it create the default VM (successfully)
• Launch Docker QuickStart terminal and it now works without any problems.

I can now launch docker instances via docker quick start term and use kitematic without any issues.

I got the solution from the link below, I assume it was caused by a conflict with an existing host only network. It's also worth noting the D-Bus error still exists, however things seem to be working fine.

#1699

Thanks @cjroth

[alrayyes]

adding 127.0.0.1 localhost to /etc/hosts seems to fix the problem for me.

[nathanleclaire]

This issue is very long and contains a lot of digressions. Please retry the faulty commands with Machine 0.5.0. If someone continues to encounter similar ones please open a new one at https://github.com/docker/machine/issues/new with detailed information including:

• Which OS you are on
• Anything atypical in networking configuration (VPN, proxy, SSH configuration settings, etc.),
• Output of the misbehaving commands with the --debug flag
• the VirtualBox logs from ~/.docker/machine/machines/name/name.

Thanks!

• N

[kopiczko]

0.5.0 works for me. Thanks!