2

I installed docker machine, and then created a new docker-machine on Windows 10.

Now I run ls to see the list of docker machines.

docker-machine ls command

Now I run the following command

docker-machine start hypervdockermachine

Now I am stuck at this

Waiting for SSH to be available... Too many retries waiting for SSH to be available. Last error: Maximum number of retries (60) exceeded

Waiting for SSH to be available problem

I have seen the git hub issue here, but not clear what to do.

Is there a way to solve this problem? I am not good at ssh

UPDATE

I just found a workaround.

You can run the above commands with git bash.

with git bash

Most important, you must run git bash as admin. Else you will end up scratching your head.

Even the basic

docker-machine ls

will not show up anything without being an admin.

Finally if you are seeing the following error

Unable to query docker version: Get https://192.168.0.105:2376/v1.15/version: x509: certificate signed by unknown authority

Then you have to look at this issue.

docker-machine regenerate-certs yourdockermachinename

If needed user --force option

VivekDev
  • 20,868
  • 27
  • 132
  • 202

1 Answers1

0

I got into the same problem after I moved .docker to partition D: and created a symlink to C:\Users\username\.docker, following this SO answer. I removed the old machines and configured new ones, and tried to regenerate the certs as suggested in the OP workaround but the problem was not solved.

After googling, I found this OpenSSH wiki page and suspected that the cause of the problem was related to permissions.

So I could solve the problem by trying two different things:

  1. Delete .ssh (source)
  2. fix permissions to D:\path\to\.docker, allowing only SYSTEM, Administrators and my user to have full control access (source). These permissions were the same defined for .docker when it was under C:\Users\username\, but moving the folder to another partition made it inherit different permissions. To avoid dealing to much with it, I keep inheritance enabled changed the permissions directly in D: rather than in .docker folder.
Bruno Arruda
  • 3
  • 2