error during connect: Get http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.38/info

Viewed 41373

System info: Windows 10 pro 64 bit

C:\WINDOWS\system32>docker --version

Docker version 18.06.1-ce, build e68fc7a

C:\WINDOWS\system32>docker info

error during connect: Get http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.38/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.

C:\WINDOWS\system32>docker pull hello-world

Using default tag: latest

Warning: failed to get default registry endpoint from daemon (error during connect: Get http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.38/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/ error during connect: Post http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.38/images/create?fromImage=hello-world&tag=latest: 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.

11 Answers

You can powerShell as admin.

Run this code:

cd "C:\Program Files\Docker\Docker"
./DockerCli.exe -SwitchDaemon

Running Powershell with elevated access solved my issue.

Usually this error means the Docker daemon that is docker services is not up and running.

  • Make sure docker is running by issuing below command in power shell in elevated mode.

    docker run hello-world

    A response as hello from docker will be printed on console.

  • Else start the docker by double clicking the docker app from start menu. Below is the snapshot of graphically up and running docker daemon.

enter image description here

On Windows, go to the folder %homepath%\.docker, open daemon.json and if debug is set to true then set it to false.

I had the same error as in the question and after I changed the above it worked again for me. After I got the error, I had been looking at the various docker settings and decided to set debug to false because I don't need any daemon debug info for what I'm doing. I don't know why it was set to true originally.

Fow Windows:

Launch command: "C:\Program Files\Docker\Docker\DockerCli.exe" -SwitchDaemon

This error is because of organisation network certificates which are installed in local machine. Beacuse some companies restricted network by installing certificates.

docker daemon service is not running on my machine and when I start the service, this error us resolved.

I had faced the same error, the following worked for me:

In the windows taskbar, the docker icon was red in color saying Out of Memory...
In the Docker Desktop App, goto

Settings -> Resources -> Disk Image Size -> decrease the space allocated -> Apply & Restart

In my case, although I had the docker service running as admin and the service was shown as running, it was not.

Open the docker desktop app, click on the 'troubleshoot' icon. Check if the service is effectively running (bottom left). If it's not, try to 'clean/purge data', and then restart the service. It worked for me!

enter image description here

Verify it by running docker run hello-world

open the docker docker . Simply upgrade the docker and then run command

docker-compose up -d

you will be able to solve the specified path error.

docker.errors.DockerException: Error while fetching server API version: (2, 'CreateFile', 'The system cannot find the file specified.') [14620] Failed to execute script docker-compose

Then after doing above task I easily sole it and solve the error

This did happen to me while i was using docker today for the first time. I fixed by opening up the docker app in the PC and signing and selecting the necessary subscription plan.

Yo,

open docker app > settings > Docker engine > "debug": true,

debug was false initially, after changing it to "true" it worked.

Thanks.

Related