Docker Community Forums

Share and learn in the Docker community.

Installation error?

(Randal Cobb) #1

I just installed boot2docker on my Mac laptop. Install went smoothly without errors, but, when launching boot2docker, I get the following error:

bash-3.2$ docker version
Client version: 1.7.0
Client API version: 1.19
Go version (client): go1.4.2
Git commit (client): 0baf609
OS/Arch (client): darwin/amd64
An error occurred trying to connect: Get dial tcp i/o timeout

I am running OS-X 10.9.5, and the Virtualbox VM IS running. Any suggestions?

Thanks in advance!

(yvesdufour) #2

I had the same issue ( and others ) upon installing boot2docker with new docker version… finally I clean up my mac ( uninstalled boot2docker, old vacant, …) and I decided to go with docker-machine

do a curl -L https at the following url : ( sorry cannot write urls… here)
/ > /usr/local/bin/docker-machine
~$ chmod +x /usr/local/bin/docker-machine
~$ docker-machine -v
machine version 0.3.0

then I installed docker
do a curl -L https with the following url : > /usr/local/bin/docker
~$ chmod +x /usr/local/bin/docker
~$ docker --version
Docker version 1.7.0, build 0baf609

and finally docker-compose do a curl -L https with the following url : -s-uname -m > /usr/local/bin/docker-compose
~$ chmod +x /usr/local/bin/docker-compose

~$ docker-compose version: 1.3.1
CPython version: 2.7.9
OpenSSL version: OpenSSL 1.0.1j 15 Oct 2014

then I created my development machine on my mac
~$ docker-machine create --driver virtual box dev

No default boot2docker iso found locally, downloading the latest release…
Downloading to /Users/yves/.docker/machine/cache/boot2docker.iso…
Creating VirtualBox VM…
Creating SSH key…
Starting VirtualBox VM…
Starting VM…
To see how to connect Docker to this machine, run: docker-machine env dev

You can verify that a machine was created like this:
~$ docker-machine ls
dev * virtualbox Running tcp://

If you want to see what variables will be exported, you can enter
~$ docker-machine env dev
export DOCKER_HOST=“tcp://"
export DOCKER_CERT_PATH=”/Users/yves/.docker/machine/machines/dev"

Run this command to configure your shell:

eval “$(docker-machine env dev)”

then you can create a remote host (I did on Digital Ocean, I created a staging machine ) if you have an account

When you run a container on this host, any ports that the container exposes are accessible at the host’s IP address. You can use the following command to get it:

$ docker-machine ip
You can start and stop the host with the following commands:

$ docker-machine stop
$ docker-machine start

If you started more than one host with Machine, you can specify the host specifically if it’s not the active one by adding the name:

$ docker-machine stop dev
$ docker-machine start dev
You can find other commands here or just enter docker-machine help

and you with from one environment (dev or remote ) just using the command
eval "$(docker-machine env dev)"
eval “$(docker-machine env staging)”

so my advice is to forget about boot2docker and go to urge Docker eco-system…
I dion’t need yet docker-swarm as I dont need clusters and docker-swarm is still in beta;… but keep an eye on it…


(Sven Dowideit) #3

There is a known timing issue with boot2docker 1.7.0, which will be resolved in the 1.7.1 release which should be available soon.