Error getting IP address: Something went wrong running an SSH command #317
Comments
|
I get the same problem on OSX 10.10.5. |
|
windows 10 failed too. windows 10 64bit Creating Machine default... |
|
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. |
|
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. |
|
@reviling would there be a way to automate this? $ docker-machine rm default
$ docker-machine create --driver virtualbox default |
|
I was able to recreate the issue by running # hack/make.shThen ctrl-c'ing out before it completed 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. |
|
I'm also experiencing this error and have the same results as @reviling, running I'm having to do this quite regularly, so if anyone has any ideas then please share them! |
|
running into the same issue here. |
|
Encountered this issue after I ran ➜ ~ 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 systemYou see, the ➜ ~ 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 systemThought 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 :
|
|
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 In debug ( If I run command manually I see: Here is solution to bad owner problem: https://superuser.com/questions/348694/bad-owner-or-permissions-error-using-cygwins-ssh-exe. |
|
I have the same error though when trying it just got stuck and never gave any output, so I went ahead and removed the default folder manually. Though when trying to run It got stuck on creating shh again, this was the output; 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??? |
|
Also getting the same issue here (El Capitan) |
|
OSX: v10.11.2 (El Capitan) The following worked for me: |
|
Also getting the same issue here |
|
+1 for @nasserahmed's link - deleting all the Host-only networks from virtual box fixed it. |
|
+1 deleting all image from virtual box fixed it. |
|
I have a work-around that I've been using for a few weeks - all the regular "docker" commands work from my terminal, and I never use docker-machine anymore. To ssh into the vm, I use the docker-ssh alias defined below. [updated, added DOCKER_HOST to file below] Put the following lines into a script in ~/bin/docker-setup. In my ~/.bashrc I source it with the command ". $HOME/bin/docker-setup" . You need to get the host ip address [ with the NAT networking, this may be 192.168.99.100. If you use Bridged networking on network interface 0, this is an IP address on your LAN on eth0 interface]. In the vm console window type "ifconfig | less" to see the network interfaces. (press Show on the Virtualbox UI if the console window is not visible). This is the only thing I ever need to do in that window. After this setup, you can just type "docker-ssh" to ssh into the boot2docker vm from your regular Terminal or iTerm window. With this setup, you can use any docker command "docker ps", "docker build" ,etc. If you use shell scripts (build.sh, or Makefile, etc.) to construct docker images, don't forget to include ${DOCKER_ARGS} on the command line in the script file. For example, Bonus tip: To start port forwarding, type "docker-ports" in a terminal window. After executing this command, docker containers can access the server at http://$DOCKER_BRIDGE_HOST_IP:7770.When setting up remote port forwarding that binds to a specific IP address, you have to enable GatewayPorts in sshd_config. In /etc/ssh/ssh_config (or /usr/local/etc/ssh/sshd_config), add the line |
|
On windows 10 - using windows command prompt shell Re-creating the machine Although I see the machine running in Virtualbox Preview UI rectangle in the upper-right corner of the window. Then the logs: What should I investigate more ? |
|
I have exactly the same issue with the same behavior as iongion has |
|
A bit more info here: I've tried it with: And the last debug log entries: So from it, a few errors: Did not find any crash report. And it does restart the machine, although command finishes with an error again. This is solved by changing your adapter properties and enabling "VirtualBox NDIS6 Bridged Networking Driver" (if not enabled) in your virtualbox network adapters. Now, I am able to restart (no more Now Ok, I try what it says: Ok, so now it is a port issue, let's check the IP address of the default machine, I go to virtualbox and click show, then One is 10.0.2.15 (this is NAT network) Let's now see if the host machine running virtualbox (a windows box) can see the last address: It does, let's telnet to know if the docker daemon find the port open for 22 does not work either, so it is not opened or not running, let's eliminate one of them, back to virtualbox gui and into the default machine screen, on bash: I see both ports are opened, telnet on the machine itself(in the
Telnet from the host machine: Ok, then there might be something in between, virtualbox network settings, let's see how port mapping works in this case. Restart for the sake of restarting: Again regenerate ? I stop here cause I have no clue what to do next, it seems that either the services are not running on this boot2docker default image or that there is a firewall or something in between that does blocks/prevents access to those ports. |
|
Managed to make it be able to execute
Apparently adding that port mapping additional rule made it work. Now docker-compose is not running. This because on windows, and on windows I cannot: Yes, I could take the env vars and export them myself in a windows compatible way, but I am too lazy. As there is no eval, I trick this by firing a POSIX shell using msys and loading the env. And back to square 0 - the infamous SSL error But this is SSL of python and from what I remember docker-compose is not python anymore. |
|
Today I got some update from Microsoft installed and Docker started working ... so try to install latest updates for Windows 10 - might work for you as well :) (PS: I had to recreate the default VM) |
|
Same issue append to me. I changed the name of the default VM to default1 (in Oracle VM VirtualBox Manager GUI), and start Docker Quickstart Terminal again (with Run as administrator), Worked! |
|
update 1.9.1f.exe ALL runs well. |
|
Update: running 'Docker Quickstart Terminal' with 'Run as administrator' solved the problem for me (Windows7) |
|
I cannot start "Docker Quickstart Terminal" or Kitematic (toolbox 1.9.1f), I have this error on Windows 8.1: Update: I deleted "host-only" network interfaces in global VirtualBox config (see docker/machine#1801 (comment)) and that fixed the problem. |
|
@bojanstef |
|
Its OS X EI Capitan. Sticking with boot2docker for now, its working well on the same box.. |
|
I tried almost all the solutions and none of them worked. But it works now and I'm pretty sure chmod on the ssh config ultimately fixed it. OS X El Capitan v10.11.2 |
|
OSX El Capitan. If it helps anyone, I had two obstacles:
After disconnecting VPN, and setting my ~/.ssh/config back to "normal", everything worked as intended. Figuring out how to run this all seamlessly is my problem :) - might just use an independent VM or Cloud Server for development instead. |
|
Did the Found a simpler solution though! Open VirtualBox, turn off the "default" machine. Run Docker Quickstart and it starts up the VM and connects fine! |
|
+1 |
|
I have met the same problem, on OSX EI Capitan. I just restarted my Mac and then it became fine. |
|
I was having the same problem. Thank you @drewlamur changing the permissions on my ssh folder helped me with the issue for know. I hope that can give a better work around for this issue. |
|
$ docker-machine rm default I just do like that. but it appear another fault: ``$ docker-machine create --driver virtualbox default who can help me ? |
|
In my case, problem was in low virtual memory. 256mb is not enough. Increasing it to 512mb have helped. There should be some error handling about out of memory or something like that at boot/loading time. |
|
See logs in virtualbox directly. If it stuck, it will show at which point it does. |
|
Same issue for me (Windows OS), in my case I solved it by opening virtualBox and resetting (Ctrl+T) "default" machine, then I opened 'Docker Quickstart Terminal Again' (It thrown the same error the first time) and ran |
|
i see. |
|
OS X El Capitan docker-machine rm default works for me |
|
OS X El Capitan I also had to run this after the ssh failed. However.
|
|
@iver3on , Were you able to find solution to your problem? I am also facing the same issue? See below: $ docker-machine rm default $ docker-machine create --virtualbox-no-vtx-check --driver virtualbox default It just get stuck there and nothing happens? Any idea? Any idea? I am using Win10 and Docker version 1.12 |
|
create a port forwarding for 57760 to 22 and it will solve problem |
|
Recreating the virtual machines seem to be pretty extreme, lol What I usually run: Specs: Maybe Related:
|
|
Just one more possible solution: Check "VBoxHardening.log" if it mentions "LavasoftTcpService.exe":
Source: |
|
Encountered same problem. Windows 7 Enterprise 64-bit
|
|
This is most of the time issue because of firewall or VPN connectivity. I would suggest to create VM after you disconnect from VPN. |
|
Before you try the below steps -
Removing the "default" machine removes all the images which are associated with it. It may be a quick fix but definitely not worth it for people who are working on images already part of their "default" machine. Please try resetting the "default" machine in VirtualBox by going to Machine-->Reset.
|
|
When I try to delete the default VM in the Virtual Box, I cannot as the option Delete is greyed when I right-click on it. How can I delete the default VM ? |
|
Finally the Delete option was available |
You don't need to remove the vm in my experience. Simply powering it off and turning it back on will work. It appears restarting your machine without shutting town the oracle vm will cause this issue. |
|
I'm also experiencing this error and have the same results, running 'docker-machine rm default' and then firing up the quickstart terminal worked for me - but I also don't know why… |
|
Hi. Maybe something similar to #887 (comment) is happening at least on other Windows machines, too... Essentially a conflict of different SSH clients being used by Docker in different shell environments or after some new software installation with bundled OpenSSH |
Hi,Do you got any soln for this |
and others
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:
What do am I doing wrong?
Thanks
The text was updated successfully, but these errors were encountered: