No IP on Docker-Machine Quickstart #2240
Comments
|
Versions: |
|
@dcunited08 Does |
|
Also, please post the output of |
|
Cleanup and VBoxManage settings: Rerunning Quickstart Script: |
|
same here on a Mac OS X |
|
+1 docker --version docker-machine --version virtual box
|
|
can you try |
|
|
|
Having the same issue here... Do you have any news or workaround related to this problem? |
|
@felipesabino this one helped me: docker-archive/toolbox#273 (comment) |
|
I am having the same issue as well. Virtually the same setup as @seregasheypak. #273 did not help me. I noticed that this happened after I restarted my computer. My VM's in VirtualBox were not shut down properly. Might have something to do with it. |
|
Exit status 255 ubiquitously implies that something went wrong with the |
|
I've managed to reproduce the issue with the following steps:
In my scenario, step 8 froze and eventually timed out trying to SSH into the box. Here's the result of the last command: I then tried to list my machines and got another ssh error: I followed @nathanleclaire's request to run Output of successful ssh: Output of failed ssh: |
|
After further testing, I have found that if I create a swarm using the "token" method instead of consul, and if I use the Parallels driver to create my VM's, then I no longer have this problem. I'm not sure which of those changes solved the problem. |
|
I've narrowed it down to a problem with VirtualBox. I have the exact same setup as before except I am using the Parallels driver and I am not having any problems. I think it has something to do with the fact that VirtualBox doesn't properly shutdown its VM's when the parent O/S restarts. They just get killed, which corrupts them somehow. |
|
@kcraft @seregasheypak those steps did not work for me either :( |
|
What's your os, virtual box version? 2015-11-25 18:27 GMT+01:00 Felipe Sabino notifications@github.com:
|
|
Mac OSX Yosemite (10.10.5) |
|
@seregasheypak mine are the same as @kcraft |
|
Mine is virtual box 5.0.8 r103449 Did you try to restart VBOX, docker, delete vm and recreate new one? 2015-11-26 1:11 GMT+01:00 Felipe Sabino notifications@github.com:
|
|
Any luck on this? Anyone found a solution? |
|
Anyone still experiencing this, please run |
|
I found that nathanleclaire's recommendation above worked, but my original Docker QuickStart Terminal |
|
Having the same issue with the versions you specified. Everything is fine until I reboot, deleting and recreating the default machine resolves the issue. |
|
@nathanleclaire @seregasheypak I just had the same problem with an almost clean OS X install, where the only thing copied from my old mac was my After I removed it, everything worked as expected. I did not try tweaking my Here is my old |
|
Same here on What fixed it was also the suggestion by @nathanleclaire (Dec 10, 2015) to run: $ docker-machine rm -f default && docker-machine --debug create -d virtualbox defaultThen, to get your shell fully configured... $ docker-machine env default
export DOCKER_TLS_VERIFY="1"
export DOCKER_HOST="tcp://192.168.99.101:2376"
export DOCKER_CERT_PATH="/Users/user/.docker/machine/machines/default"
export DOCKER_MACHINE_NAME="default"
# Run this command to configure your shell:
# eval $(docker-machine env default)
$ eval $(docker-machine env default)You should now be able to run |
|
@globalcitizen agreed that nobody should remove their SSH configuration to be able to set up Docker/VirtualBox, but as you can see through my previous interactions, what fixed your problem did not work for me - #2240 (comment) and #2240 (comment) - even with the last VirtualBox version and, as ludicrous as it might sound, removing my SSH config did work. |
|
I had this problem, it turned out to be a corrupt ~/.ssh/config file on my mac. I had mapped my ~/.ssh folder to a container that had appended some stuff to the end of it without inserting a new line, causing a syntax error. Thanks to @felipesabino , I never would have found the issue without the info here! |
|
Did the Found a simpler workaround though! Open VirtualBox, turn off the "default" machine. Run Docker Quickstart and it starts up the VM and connects fine! |
|
Just FYI everyone, if Docker Machine's implicit use of |
|
I don't have a
This was produced by a clean |
|
@jurjevic Any chance I could get you to cobble together a SSH command directly based on that debug output and print the result of running it with e.g: $ /usr/bin/ssh -vvv -o BatchMode=yes -o PasswordAuthentication=no -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o LogLevel=quiet -o ConnectionAttempts=3 -o ConnectTimeout=10 -o ControlMaster=no -o ControlPath=none docker@127.0.0.1 -o IdentitiesOnly=yes -i /Volumes/Extern/Docker/Machine/machines/default/id_rsa -p 51788
...Make sure to set the port correctly. |
|
Going to close this issue as it's veered off the rails from the original topic, but it's OK to keep posting here. |
|
adding another scenario, just in case. |
|
I have a similar problem, where my docker-machine will loose its connection. When I first start it, it works fine, but sometime during the day it will loose the connection. To reconnect I have to kill the VM in VirtualBox and rerun the quickstart terminal. I am using docker-machine.exe version 0.7.0, build a650a40 on Windows 10 with VirtualBox Version 5.0.16 r105871
Thanks for your help |
|
same. |
|
@justechn I have the same problem with you, have you fixed it ? |
|
@chengjianhua-genedock I have not found a solution. |
|
sad...I continue to find resolution, if you find out, please tell me,thanks ~ On Tue, Jul 19, 2016 at 3:35 AM +0800, "justechn" <notifications@github.commailto:notifications@github.com> wrote: @chengjianhua-genedockhttps://github.com/chengjianhua-genedock I have not found a solution. ― |
|
I had fixed it by reinstall win10 preview to win10 pro. |
|
Same problem, no IP... |
|
Anyone hitting the "No IP" problem, you might wanna try uninstalling and re-installing VirtualBox specifically (restarting your host computer probably couldn't hurt either). I've hit quite a few issues unfortunately with upgrades not going super smoothly without this uninstall. |
|
I face the no IP issue on a Windows 10 VM hosted in iMac. |
|
Above from nathan doesn't change anything on windows 10. If I new what port windows should be connecting to the VM on I could just portmap it. How do I find that port? Is it the TCPIP one listed by netstat on the boot2docker? By the way on the retry under docker the console for boot2docker did not come up. |
|
Cool. I had two network adapters for host only. Picking the other one helped. Then I ran into a connection failure that showed me the port so I port mapped it on the Network NAT. Don't know if that helped or not. Then I got some blather about certs not being correct and the helpful advise to regenerate them. Then lastly I got the information that on Windows 10 I need to run elevated to connect. So restarting quick start running as admin finally allowed a docker ps to get through. Hurray! |
|
I had the same problem as @ghost above. Regarding virtualbox and more cores/CPU:s than one. I have Mac Pro with 8 cores from 2008 that does only supports the Docker Toolbox and not the new Docker for mac. Using Virtualbox 5.2.6. I tried to increase the number of cores of the virtual machine to 8 CPU:s to match my physical cores ( My solution was to use the Parallels driver instead of Virtualbox since I had Parallels Desktop already installed: https://github.com/Parallels/docker-machine-parallels . I created a machine with the maximum number of CPU:s and then later starting the machine with: |
|
Just restart : Docker Quickstart Terminal It fixed the same problem for me Worked like a charm |
and others
I ran the quickstart and had the following output:
The text was updated successfully, but these errors were encountered: