Installation of Docker Toolbox on Mac: Error loading driver "virtualbox": dial tcp: missing address

[bdfasching]

When installing 1.9b of the docker toolbox on mac (10.10.5), installation completes correctly but when first starting Docker Quickstart Terminal I get the following message and it seems the default docker vm is not created:

bash --login '/Applications/Docker/Docker Quickstart Terminal.app/Contents/Resources/Scripts/start.sh'

Creating Machine default...
Error loading driver "virtualbox": dial tcp: missing address
Host "default" does not exist
Starting machine default...
Could not load host "default": Loading host from store failed: Host does not exist: "default"
Setting environment variables for machine default...

.

## ## ==

## ## ## ## ===

/"""""""""""""""""_**/ ===

____** o **/ 
\ \ **/ 
\****_______/

Could not load host "default": Loading host from store failed: Host does not exist: "default" 
docker is configured to use the default machine with IP 
For help getting started, check out the docs at https://docs.docker.com
## Host "default" does not exist 

open for any help! 
Thanks!

[msound]

@bdfasching I think you need to run Kitematic first, and that will create the default vm.

[bdfasching]

no dice. Tried running Kitematic after a reinstall of the tool kit and get the following:

/usr/local/bin/docker-machine -D create -d virtualbox --virtualbox-memory 2048 default returned non zero exit code. Stderr: Docker Machine Version: 0.5.0 (04cfa58) Found binary path at /usr/local/bin/docker-machine-driver-virtualbox Launching plugin server for driver virtualbox Plugin server listening at address Error loading driver "virtualbox": dial tcp: missing address

I get the same original issue above on the terminal as well.

[AndrewSmiley]

Same issue with me

[jikkujose]

@msound that worked. But wish the entire process can be fully done via the command line.

[coke]

Got the same error on my machine. Running kitematic generated the same error.

[coke]

This is on 1.9.0d on the 10.10.5 OS

[muellers7]

go to /Users/YOUR_USER/.docker/machine/certs/ and just delete the file/files inside. Then restart kinematic and it should work (at least for me it did).

[bdfasching]

@muellers7 I only have cache and machines under .docker. no certs directory and nothing under machines...

Tried 19.0d on 10.10.5 as well along with virtualBox 5.0.10 and still get same error. Any other way to troubleshoot this issues with logs or replacing virtual-box drivers...

[aelaibi]

Got the same error !
can any one help us

I'm using 1.9.0d

[coke]

So, I think it might be related to the antivirus running on my $DAYJOB machine.

The applications don't work, but if I run this:

DYLD_INSERT_LIBRARIES= /Applications/Docker/Docker\ Quickstart\ Terminal.app/Contents/Resources/Scripts/start.sh

Then it seems to run ok - I get a shell where docker-machine and docker both work. (If you don't use the start script, you end up having to use DYLD_INSERT_LIBRARIES on each invocation, which is painful).

[bdfasching]

Looks like this is a big step in the right direction. Confirmed I can run the quickstart terminal now as long as DYLD_INSERT_LIBRARIES is set as above.

Kitematic still doesn't work, I get the following error:

/usr/local/bin/docker-machine status default returned non zero exit code. Stderr: fatal error: runtime: bsdthread_register error runtime stack: runtime.throw(0x5ddba0, 0x21) /usr/local/go/src/runtime/panic.go:527 +0x90 fp=0x7fff5fbff580 sp=0x7fff5fbff568 runtime.goenvs() /usr/local/go/src/runtime/os1_darwin.go:73 +0x8d fp=0x7fff5fbff5a8 sp=0x7fff5fbff580 runtime.schedinit() /usr/local/go/src/runtime/proc1.go:60 +0x83 fp=0x7fff5fbff5f0 sp=0x7fff5fbff5a8 runtime.rt0_go(0x7fff5fbff620, 0x3, 0x7fff5fbff620, 0x0, 0x3, 0x7fff5fbff7b0, 0x7fff5fbff7ce, 0x7fff5fbff7d5, 0x0, 0x7fff5fbff837, ...) /usr/local/go/src/runtime/asm_amd64.s:109 +0x132 fp=0x7fff5fbff5f8 sp=0x7fff5fbff5f0

Thanks

[mariorodriguespt]

+1

[lachholden]

+1 on windows 8.1 with virtualbox 5.0.12 and docker toolbox 1.9.1g, except it fails during the creation and makes no attempt to start the vm

[ajbeach2]

@bdfasching
I have the same error. I think you may have digital guardian or similar running on your machine.

see:
https://groups.google.com/forum/#!topic/golang-nuts/HtcZc3wO-rw

[coke]

I ended up switching to docker-machine + VMware fusion, no issues.

[jmorganca]

Hi all - thanks for the issue. This seems to be a specific issue with VirtualBox and docker-machine.

Merging this with #153

For more details and for a better conversation, please see the docker/machine repo.

Thanks again

[hungdm9999]

in my case, docker-machine was block outgoing attempt. Start Vbox, remove default machine, allow docker-machine on firewall works for me.