Docker warning: Failed to get default registry endpoint from daemon

On Windows 10, when I call the docker command:

docker pull mongo:windowsservercore 

I get the following output:

 Warning: failed to get default registry endpoint from daemon (error during connect: Get http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.26/info: open //./pipe/docker_engine: The system cannot find the file specified. In the default daemon configuration on Windows, the docker client must be run elevated to connect. This error may also indicate that the docker daemon is not running.). Using system default: https://index.docker.io/v1/ 

When I docker-machine create default

 (default) Waiting for an IP... Error creating machine: Error in driver during machine creation: Too many retries waiting for SSH to be available. Last error: Maximum number of retries (60) exceeded 
+14
windows docker docker-machine
source share
5 answers

You are probably using Docker for Windows . An OpenSource solution for running Docker on Windows 10. In this case, the reason is that your Docker CLI cannot work without a daemon. Launch the Docker daemon (you probably have a desktop icon), and as soon as it reports that it is ready, try your commands again.

+10
source share

I got the same error as Docker for Windows in Windows 10 Pro. The solution was to open Docker settings and enable Daemon. Right-click the taskbar icon and select options. Then turn on the daemon in the image below.

Option To Choose

+6
source share

This was allowed for me and was able to install once a right-click on the taskbar and clicked the "Switch to Windows Container" button.

+2
source share

I just restarted docker in Windows from the tray icon, right click, then "Restart".

+2
source share

I am getting this error too. I installed docker through the docker toolbar. I tried the windows docker installer, but it said that I need a pro version of Windows 10 (there is a home version of win10).

In any case, if I run commands through the Docker quick launch terminal, this problem disappears. i.e. use the docker quickstart terminal instead of the command line.

0
source share

All Articles