Could not create machine in docker

Question

I just installed docker on my Windows 7 machine. When I start Docker QuickStart, I get the following error, which seems to be created when the machine is created:

Creating machine... (default) Unable to get the latest Boot2Docker ISO release version: Get https:/ /api.github.com/repos/boot2docker/boot2docker/releases/latest: dial tcp 192.30.2 52.124:443: connectex: A connection attempt failed because the connected party d id not properly respond after a period of time, or established connection failed because connected host has failed to respond. (default) Copying C:\Users\robot\.docker\machine\cache\boot2docker.iso to C:\Use rs\robot\.docker\machine\machines\default\boot2docker.iso... (default) Creating VirtualBox VM... (default) Creating SSH key... Error attempting heartbeat call to plugin server: read tcp 127.0.0.1:60733->127. 0.0.1:60732: wsarecv: An existing connection was forcibly closed by the remote h ost. Error attempting heartbeat call to plugin server: connection is shut down Error attempting heartbeat call to plugin server: connection is shut down Error attempting heartbeat call to plugin server: connection is shut down Error attempting heartbeat call to plugin server: connection is shut down Error creating machine: Error in driver during machine creation: read tcp 127.0. 0.1:60733->127.0.0.1:60732: wsarecv: An existing connection was forcibly closed by the remote host. Looks like something went wrong... Press any key to continue... 

Answer 1

A similar problem exists in docker / machine / issues / 2773 .

Try to check if the problem persists when creating the machine yourself, instead of using the quick start:

Find where docker-machine.exe was installed (or copy the last one released in %PATH% ) and use this from a regular CMD session:

First check your existing computer:

 # find the name of the machine created. docker-machine ls docker-machine env --shell cmd <nameOfTheMachine> docker machine ssh <nameOfTheMachine> 

Then try creating a new one:

 docker-machine create -d virtualbox <aNewMachine> docker-machine env --shell cmd <aNewMachine> docker machine ssh <aNewMachine> 

Answer 2

I have no solution, but he found the root cause.

I installed boot2docker and used it for several months. I created all my Vbox images in the same folder all the time.

One fine day, I decided to archive my machines and changed the folder in which I created the vbox images. He began to give this wired error. I returned my archive and tested it again. He began to work normally.

The difference that I found on both settings was in the archive folder, it skipped the step of creating a CA certificate and directly created the machine. In the new folder, he created the certificate, and then created the machine. It seems that the server does not like the new certificates !!!!