Unable to run docker-machine due to SSH error #2740
Comments
|
Your config file seems like it's gone sideways. My recommendation would be to upgrade to Machine 0.5.5, destroy and re-create the machine. If that doesn't work please re-open. Thanks! |
|
i have same issues, is there any solution that i don't have to delete the machine because i use it in production. |
|
@particle4dev What's the (sanitized output -- make sure not no API keys are present) of |
|
OK, there seems to be something that went sideways in a migration. That bit above where it says |
|
Works like a charm. Thank you so much :). It seems like when i open kitematic app, it overwrite config files. |
|
You're welcome @particle4dev ! KM shouldn't re-write config files (especially for non- |
|
Hi @nathanleclaire , I am having a similar issue. Should I destroy and re-create the machine? Error getting IP address: Something went wrong running an SSH command! Here is the output for |
If you can, that is the simplest solution. |
|
It worked!! awesome thanks @nathanleclaire |
|
👍 |
|
this happened to me twice today with docker-machine version 0.6.0, build e27fb87. i added those back to the config and everything seems to be running fine again. so, to me this sounds like a bug. |
|
same here. pretty annoying. |
|
The problem persists, even after updating Docker Machine. I'm thinking maybe we should reopen this one. |
|
I had the problem too today. As it turned out that I had two different docker-machine versions in place (one was called by a bash script which had an old docker-machine version in the path) and the old one always was overwriting the confif file whenever docker-machine ip [NAME] was used. |
|
@nathanleclaire - Sounds like this is definitely a bug, any plan to reopen this issue? |
|
@gregory Can you provide an end-to-end dupe? Does the issue happen with newly created machines as well? |
|
It's pretty easy to reproduce:
|
|
Thanks @recht -- Unfortunately 0.4.2 isn't forwards compatible and running https://github.com/docker/machine/blob/master/libmachine/host/migrate.go#L65 was introduced to prevent using older Machine versions it but 0.4.2 did not contain this fix. |
|
This happened to me right after changing the configuration of my VM's networking from NAT to Bridged. I don't see a The weird thing is, I can still Should I change the networking back to NAT? EDIT: |
|
WOW! Just WOW! So this is why I am having problems with my Docker Machines. Thanks. |
|
Had same problem, but turns out editing My Still getting this error, but at least, works I don't know what's causing this |
|
@GabLeRoux If possible, I'd highly suggest removing the machine and starting over from scratch (make sure to use the latest version of Docker Machine). |
|
Deleting this vm isn't a solution for me as I've worked on a wordpress container and I still need to figure out how to handle data inside this vm, I don't want to lose this data. At least, I got it working even tough it's complaining with the error I mentioned above. I used Kitematic app and I think kitematic updated the config and broke things. I am now able to see wordpress but It seems to redirect me to 192.168.99.101 so maybe the machine ip changed for some reason once. I'll try to change my machine ip and see what happens. At least, I'm able to access data now so it should be alright :) Edit: happened again using Kitematic :( |
|
Getting these same errors when trying to run
More Error Details: https://gist.github.com/richnsoos/8046721ec4f68951d20e Before running the command, I:
To those who might be able to help, here's my setup:
These error are repeatable. If I delete the docker-machine and start fresh with same steps, I get the same errors. Thank you in advance! 3/7/16 Update: after re-running the same steps at work, docker was successfully up and running. I guess running these steps at home, through the VPN is what was causing problems. Thank you |
|
This is still an issue with v0.6.0 - even if I try running |
|
@jurjevic Did you try 0.7.0? |
|
I got the similar issue. It is funny that the reason was just a file named ssh.bat in the current directory. |
|
I have the same error then I modified config.json : add SSHKeyPath ,SSHPort, It works now. docker-machine: 0.5.0 |
|
$ docker-machine create -d virtualbox default Details: 00:00:00.774486 Power up failed (vrc=VERR_INTNET_FLT_IF_NOT_FOUND, rc=E |
|
I got the same error as below today
then i tried docker machine stop and start and it works for me keeping my images intact. $ docker-machine stop |
|
I had the same issue with my Docker-Toolbox on Windows 7. I'm using docker in combination with VirtualBox. Docker versionError causeIt was a missing port forwarding rule in VirtualBox which I removed accidentally FixThis steps fixed this issue for me:
|
This solved it for me but the -v command showed port 22 so I mapped 22 to 22 in the port forwarding settings. |
|
I'm running Ubuntu 16.04 via virtualbox on a Windows 10 machine. I installed docker and docker-machine using the instructions on the docker get-started site. $ docker-machine create --virtualbox-no-vtx-check --driver virtualbox myvm1 $ docker-machine ssh myvm1 -v |
can you please say how to do it |
|
I have the same issue. Is there a solution?
[issue] Permission denied PS C:\Users> docker-machine ssh master1 -v PS C:\Users> docker-machine ls --filter state=Running |
and others
Running any cmd against docker machine is failing due to an issue finding SSH keys on the machine (or so the error msg says). Regenerate certs does not fix the problem. Please see the logs attached below.
OS: OS X Yosemite
VBox: VirtualBox 5.0.6 r103037
Docker Machine: 0.5.2
Basic msg
Msg with debug flag
The text was updated successfully, but these errors were encountered: