We decided to test Docker to see what all of the hype was about. After some tweaking we manage to get it going on windows 10 .

We downloaded and installed the Docker Toolbox for Windows. Initially we wanted to avoid using virtualbox until we could migrate our DNS VM from Hyper-V. So we created a boot2docker vm in hyper-V using the following from the command line.

docker-machine create –driver hyperv boot2docker

After which we attemnpting to set the env for docker-maching . This allows docker-machine to connect to the new VM running the docket daemon.

C:\WINDOWS\system32>docker-machine env –shell cmd vm
Error checking TLS connection: Error checking and/or regenerating the certs: There was an error validating certificates for host “”: open C:\Users\Mas\.docker\machine\machines\vm\server.pem: The system cannot find the file specified.
You can attempt to regenerate them using ‘docker-machine regenerate-certs [name]’.
Be advised that this will trigger a Docker daemon restart which will stop running containers.

C:\WINDOWS\system32>docker-machine regenerate-certs vm

Regenerate TLS machine certs? Warning: this is irreversible. (y/n): y
Regenerating TLS certificates
Waiting for SSH to be available…
Detecting the provisioner…
Copying certs to the local machine directory…
Copying certs to the remote machine…
Setting Docker configuration on the remote daemon…

C:\WINDOWS\system32>docker-machine env –shell cmd vm
SET DOCKER_CERT_PATH=C:\Users\Mas\.docker\machine\machines\vm
REM Run this command to configure your shell:
REM FOR /f “tokens=*” %i IN (‘docker-machine env –shell cmd vm’) DO %i

Now we can connect to the new vm from the command line. Thanks to

C:\WINDOWS\system32>docker-machine ssh vm

Additional information



PS C:\Users\user> docker images
An error occurred trying to connect: Get http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.23/images/json: open //./pipe/docker_e
ngine: The system cannot find the file specified.

Fix : run  docker-machine regenerate-certs vm

volumes ?

Computer , server issues and solutions