WojtekKozaczynski
commented
7 years ago It looks like the issue is between OpenSSH and the docker-machine on Windows 10.
I have installed OpenSSH to enable remote PowerShell connections with Linux boxes (see installation guidelines @ https://github.com/PowerShell/Win32-OpenSSH/wiki/Install-Win32-OpenSSH).
I have uninstalled OpenSSH, removed a reference to its binary from the Path system variable, and now the "docker-machine create ..." command completes ( ?! ).
The sequence of debug messages for creating SSH connection to the new VM now looks like this:
Getting to WaitForSSH function...
(worker1) Calling .GetSSHHostname
(worker1) DBG | [executing ==>] : C:\WINDOWS\System32\WindowsPowerShell\v1.0\powershell.exe -NoProfile -NonInteractive ( Get-VM worker1 ).state
(worker1) DBG | [stdout =====>] : Running
(worker1) DBG |
(worker1) DBG | [stderr =====>] :
(worker1) DBG | [executing ==>] : C:\WINDOWS\System32\WindowsPowerShell\v1.0\powershell.exe -NoProfile -NonInteractive (( Get-VM worker1 ).networkadapters[0]).ipaddresses[0]
(worker1) DBG | [stdout =====>] : 192.168.0.106
(worker1) Calling .GetSSHPort
(worker1) DBG |
(worker1) DBG | [stderr =====>] :
(worker1) Calling .GetSSHKeyPath
(worker1) Calling .GetSSHKeyPath
(worker1) Calling .GetSSHUsername
SSH binary not found, using native Go implementation
&{{{<nil> 0 [] [] []} docker [0xc8a0d0] <nil> []} 192.168.0.106 22 <nil> <nil>}
About to run SSH command:
exit 0
SSH cmd err, output: <nil>:It appears that when the script cannot locate an SSH binary it falls back on a native Go implementation (whatever that is), which works.
I will open a separate issue with the PowerShell/Win32-OpenSSH folks, and I probably should also open a separate issue like "docker-machine does not work with OpenSSH on Windows 10" in this repo.
Cheers, Wojtek
MCord
feryardiant
dherges
ccac001
saalmaan
pmaoui
nitinaintahero
NiyazNz
GZFrankPeng
ilatypov
While creating a Hyper-V VM on a Windows 10 machine the docker-machine gets stuck on creating a SSH session to that VM.
My Environment
Description
I have enclosed a file ([createCommand.txt (https://github.com/docker/machine/files/908025/createCommand.txt)) with the messages from executing the following command
Everything looks fine until the script tries to open a SSH session to the newly created VM. Each attempt looks like this
and after 60 such attempts the script quits with the message
The VM is created, it is given an IP address, and it starts. The interesting part is that I can create SSH session from the command line using exactly the same SSH commands as in the script (I have enclosed a file sshConnection.txt with debug messages from execution of that command)
This means that SSH server works fine on the VM and the certificate checks out. Just for completeness I tested creating a SSH session from the VM to the Windows 10 host machine, and it also works fine. Also, after reading a few posts, I turned the firewall off but the problem still persists.
Below is what I get when I ask the docker-machine to (a) list the VM docker hosts and (b) create SSH session to the new VM
Notice that the 255 exit status is the same as in the create script.
Why does the same SSH command fail when executed in a docker-machine script and succeeds when executed from the command line? How do I further debug the issue?
Cheers, Wojtek