Error getting IP address: Something went wrong running an SSH command

Hi all
I downloaded docker-machine from https://www.docker.com/docker-toolbox and installed on my mac os x el captain version 10.11. I followed the tutorials on the site and it worked fine.
Then today I start my computer and want to download mysql from docker hub.
I start Docker Quickstart Terminal and on the console, then it shows to me:

Machine default already exists in VirtualBox. 
Setting environment variables for machine default...
                    ##         .
              ## ## ##        ==
           ## ## ## ## ##    ===
       /"""""""""""""""""\___/ ===
  ~~~ {~~ ~~~~ ~~~ ~~~~ ~~~ ~ /  ===- ~~~
       \______ o           __/
         \    \         __/
          \____\_______/
Error getting IP address: Something went wrong running an SSH command!
command : ip addr show dev eth1
err : exit status 255
output : 
docker is configured to use the default machine with IP For help getting started, check out the docs at https://docs.docker.com 

Error running connection boilerplate: Error getting driver URL: Something went wrong running an SSH command!
command : ip addr show dev eth1
err : exit status 255
output :

What do am I doing wrong?
Thanks

[draeb]

I get the same problem on OSX 10.10.5.

[baoming]

windows 10 failed too.

windows 10 64bit
toolbox 1.9.1a

Creating Machine default...
Running pre-create checks...
Creating machine...
(default) OUT | Creating VirtualBox VM...
(default) OUT | Creating SSH key...
(default) OUT | Starting VirtualBox VM...
(default) OUT | Starting VM...
Error creating machine: Error in driver during machine creation: Too many retries waiting for SSH to be available. Last error: Maximum number of retries (60) exceeded
Looks like something went wrong... Press any key to continue...

[owlas]

I have the same set up as kostonstyle and have also had the same problem. I loaded the quickstart terminal once and all was working, I then reloaded the terminal and it has thrown this error ever since.

[draeb]

I don't know why this worked (I'm new to docker), but removing the default vm and then reloading the quickstart terminal (creates a new default vm) worked for me.

[bojanstef]

@reviling would there be a way to automate this?

$ docker-machine rm default
$ docker-machine create --driver virtualbox default

[bojanstef]

I was able to recreate the issue by running

# hack/make.sh

Then ctrl-c'ing out before it completed
From: http://docs.docker.com/opensource/project/set-up-dev-env/
Specifically without "binary" at the end.

Machine default already exists in VirtualBox.
Setting environment variables for machine default...

                        ##         .
                  ## ## ##        ==
               ## ## ## ## ##    ===
           /"""""""""""""""""\___/ ===
      ~~~ {~~ ~~~~ ~~~ ~~~~ ~~~ ~ /  ===- ~~~
           \______ o           __/
             \    \         __/
              \____\_______/


docker is configured to use the default machine with IP 192.168.99.100
For help getting started, check out the docs at https://docs.docker.com

Error running connection boilerplate: Error checking and/or regenerating the certs: There was an error validating certificates for host "192.168.99.100:2376": tls: DialWithDialer timed out
You can attempt to regenerate them using 'docker-machine regenerate-certs name'.
Be advised that this will trigger a Docker daemon restart which will stop running containers.

[marklocker]

I'm also experiencing this error and have the same results as @reviling, running docker-machine rm default and then firing up the quickstart terminal worked for me - but I also don't know why…

I'm having to do this quite regularly, so if anyone has any ideas then please share them!

[ewilliam]

running into the same issue here. docker-machine rm default works, though annoying.

[bobbypriam]

Encountered this issue after I ran docker pull training/sinatra, I don't know if it's relevant, but here are the full output of my terminal:

➜  ~  docker pull training/sinatra
Using default tag: latest
latest: Pulling from training/sinatra
d634beec75db: Pull complete
27fb5491e391: Pull complete
8e3415728a3f: Pull complete
630b03963440: Pull complete
962115fdbb58: Pull complete
9ea38b02c228: Pull complete
e20166048ece: Extracting [========================================>          ] 51.25 MB/62.67 MB
8b16a891bd1a: Download complete
Pulling repository docker.io/training/sinatra
f0f4ab557f95: Error pulling image (latest) from docker.io/training/sinatra, mkdir /mnt/sda1/var/lib/docker/graph/_tmp/acc5caf9b5f0080306956f9b43ae9106345e0ec675ae6e144e7ae869fa24811b: read-only file system 6e144e7ae869fa24811b: read-only file system
Error pulling image (latest) from docker.io/training/sinatra, mkdir /mnt/sda1/var/lib/docker/graph/_tmp/acc5caf9b5f0080306956f9b43ae9106345e0ec675ae6e144e7ae869fa24811b: read-only file system

You see, the e20166048ece: Extracting... part got stuck for a while and then the error pops out. I also tried one more time, but it gives me just the error.

➜  ~  docker pull training/sinatra
Using default tag: latest
latest: Pulling from training/sinatra
d634beec75db: Pulling fs layer
Pulling repository docker.io/training/sinatra
f0f4ab557f95: Error pulling image (latest) from docker.io/training/sinatra, mkdir /mnt/sda1/var/lib/docker/graph/_tmp/5d52c3b63b2a7c79b27a4d0d79ad4b544a6aacec467e6e35bb1847cb31e92097: read-only file system 6e35bb1847cb31e92097: read-only file system
Error pulling image (latest) from docker.io/training/sinatra, mkdir /mnt/sda1/var/lib/docker/graph/_tmp/5d52c3b63b2a7c79b27a4d0d79ad4b544a6aacec467e6e35bb1847cb31e92097: read-only file system

Thought the machine has stopped, so I checked, and here's where I encounter the error:

➜  ~  docker-machine start default
Machine "default" is already running.

➜  ~  docker-machine status default
Running

➜  ~  docker-machine ip default
Error getting IP address: Something went wrong running an SSH command!
command : ip addr show dev eth1
err     : exit status 255
output  :

docker-machine rm default and docker-machine create --driver virtualbox default fixed it, though... but my local images are lost! I'm still new to Docker so I find this confusing.

[illagrenan]

I have same issue on Windows 8.1.

docker --version
Docker version 1.9.1, build a34a1d5
docker-machine --version
C:\Program Files\Docker Toolbox\docker-machine.exe version 0.5.2 ( 0456b9f )
docker-compose --version
docker-compose version 1.5.2, build e5cf49d

// EDIT

Output of docker-machine ls is:

NAME      ACTIVE   DRIVER       STATE     URL   SWARM   ERRORS
default   -        virtualbox   Running                 Something went wrong running an SSH command!
command : ip addr show dev eth1
err     : exit status 255

In debug (docker-machine -D ls) mode I see:

...
(default) DBG | GuestAdditionsVersion="5.0.10 r104061"
(default) DBG | GuestAdditionsFacility_VirtualBox Base Driver=50,1449512600037
(default) DBG | GuestAdditionsFacility_VirtualBox System Service=50,1449512617542
(default) DBG | GuestAdditionsFacility_Seamless Mode=0,1449512600037
(default) DBG | GuestAdditionsFacility_Graphics Mode=0,1449512600037
(default) DBG | }
(default) DBG | STDERR:
(default) DBG | {
(default) DBG | }
(default) DBG | Using SSH client type: external
(default) DBG | About to run SSH command:
(default) DBG | ip addr show dev eth1
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
(default) DBG | SSH cmd err, output: exit status 255: cygwin warning:
...

If I run command manually I see:

ssh ip addr show dev eth1
Bad owner or permissions on /cygdrive/c/Users/<USERNAME>/.ssh/config

Here is solution to bad owner problem: https://superuser.com/questions/348694/bad-owner-or-permissions-error-using-cygwins-ssh-exe. docker-machine is working for me right now.

[vblackburn]

I have the same error though when trying

docker-machine rm default

it just got stuck and never gave any output, so I went ahead and removed the default folder manually. Though when trying to run

docker-machine create -d virtualbox default

It got stuck on creating shh again, this was the output;

Running pre-create checks...
Creating machine...
(default) Creating VirtualBox VM...
(default) Creating SSH key...
Error creating machine: Error in driver during machine creation: /usr/local/bin/VBoxManage modifyvm default --firmware bios --bioslogofadein off --bioslogofadeout off --bioslogodisplaytime 0 --biosbootmenu disabled --ostype Linux26_64 --cpus 1 --memory 1024 --acpi on --ioapic on --rtcuseutc on --natdnshostresolver1 off --natdnsproxy1 off --cpuhotplug off --pae on --hpet on --hwvirtex on --nestedpaging on --largepages on --vtxvpid on --accelerate3d off --boot1 dvd failed:
VBoxManage: error: The machine 'default' is already locked for a session (or being unlocked)
VBoxManage: error: Details: code VBOX_E_INVALID_OBJECT_STATE (0x80bb0007), component MachineWrap, interface IMachine, callee nsISupports
VBoxManage: error: Context: "LockMachine(a->session, LockType_Write)" at line 493 of file VBoxManageModifyVM.cpp

The default folder is created though it still has the same SSH error. I've tried uninstalling and reinstalling the docker toolbox multiple times and nothing is changing, any suggestions???

[tomphp]

Also getting the same issue here (El Capitan)

[nasserahmed]

OSX: v10.11.2 (El Capitan)
Virtualbox: 5.0.10r104061
Docker version 1.9.1, build a34a1d5

The following worked for me:
docker-archive-public/docker.machine#1801 (comment)

[udoless]

Also getting the same issue here

[tomphp]

+1 for @nasserahmed's link - deleting all the Host-only networks from virtual box fixed it.