docker error during connect — deamon is not running on Windows 10

I am using Windows 10 pc. Recently I have downloaded docker for Windows and it was working fine. But, recently a problem occurred and is it not start anymore it just hang in the status starting.

I haven’t changed any configuration and I am wondering what may cause this problem.

I use the latest version of docker.

On my pc, Hyper-V is enabled and Containers are disabled. (Since, I son’t use Windows container, I don’t think it is necessary. )

On task bar, when I check docker icon. It is always in starting status.

When I check services, it seems it is running.

when I try docker command on powershell. It could not found docker command.

I am not in an urgency to set up docker, I was just playing with it. But, suddenly this problem occured. I have been trying to solve this problem for a while. I have search similar problems and uninstall docker several times while searching for a solution. It is wierd and disturbing that a tool suddenly stop working and there is no trace to find the root problem. I suspect may be company sucurity policy change effects my computer and cause this problem But I could not find any clue to support this.

My question is what should I do to understand what is wrong. What cause the problem and how can it be fixed.

Note: When I restart computer following error occurs.

content of the error message:

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

at Docker.Backend.DockerDaemonChecker.Check(Func`1 isDaemonProcessStillRunning) in C:\gopath\src\github.com\docker\pinata\win\src\Docker.Backend\DockerDaemonChecker.cs:line 63 at Docker.Core.Pipe.NamedPipeServer.<>c__DisplayClass9_0.b__0(Object[] parameters) in C:\gopath\src\github.com\docker\pinata\win\src\Docker.Core\pipe\NamedPipeServer.cs:line 47 at Docker.Core.Pipe.NamedPipeServer.RunAction(String action, Object[] parameters) in C:\gopath\src\github.com\docker\pinata\win\src\Docker.Core\pipe\NamedPipeServer.cs:line 145

When I run docker ps -a following error occurs.

Docker for Desktop error during connect: Post A connection attempt failed because the connected party did not properly

I have freshly installed Docker for Desktop Edge in Windows 10 Home and try to build an image using the docker build command. But unfortunately, it didn’t work for me, and got the below error :

CMD — docker build -t heet1996/post:0.0.1 .

Earlier I was using a docker toolbox so I had to remove all the environment variables related to the Docker in my User variables before installing Docker for Desktop. After a lot of search on GitHub issues, I am still not getting the solution.

This is what I found in my service.txt file (C:\ProgramData\DockerDesktop\service.txt)

[18:27:22.232][LoggingMessageHandler][Info ] [f9b6b957] POST http://localhost/dns/refresh-hosts -> 204 NoContent (took 118ms)

4 Answers 4

Try to run it on Docker CLI instead of CMD

Open Powershell as Administrator and run the below commands

cd «C:\Program Files\Docker\Docker»

Docker for windows must have:

• [✓] Updated Windows 10 version >=2004
• [✓] WSL 2 and Default Distro (i.e ubuntu)

The steps are well documented here. These are what to do after the installation:

1. To confirm ubuntu’s installation, open C:/Windows/System32/bash.exe aka bash .
2. To test if docker is properly installed, run docker version on bash . This should print the docker client and server engine.
3. After successfully tested and confirmed the installations, try entering your command

here we are talking about using Docker with PowerShell and not with WSL. And also following the addition of variables in the environment variables of Windows.

Configuration when this response was made:

• Windows 10 Pro 20H2 (Build 19042.867)
• Docker 20.10.5
• Powershell 5.1.19041.610

I also had to configure docker in a dirty way too much, after several hours of research and a comparison of installation on a clean Windows 10 I understood where my error was.

In addition to the user environment variable also make sure that you do not have DOCKER variables in the Windows system environment variables either.

Here is where my error was, I think it was due to the installation of the Docker module

I had the DOCKER_HOST variable in my system variable environment, so i deleted it.

If you want to check all your environment variables with Powershell:

If you really want a Docker fresh installation on Windows, you need to delete the following folders:

my error, therefore, produced this error:

ERROR ==> error during connect: Get http://docker.artofshell:2376/v1.24/version: dial tcp: lookup docker.artofshell: no such host

After a complete uninstall of all docker (Via chocolatey, official docker . ) and by properly installing Docker from the official executable here everything is back to normal

Then if you want to use docker via Powershell you have to change the configuration of DockerCLI as you can see on many answers

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

Comments

Venkateshkuntla commented Mar 13, 2018

Expected behavior

Actual behavior

Information

• Diagnostic ID from «Diagnose & Feedback» in the menu.
• a reproducible case if this is a bug, Dockerfiles FTW
• page URL if this is a docs issue or the name of a man page
• host distribution and version (Windows version, build number, etc)

Steps to reproduce the behavior

The text was updated successfully, but these errors were encountered:

heidricha commented Mar 13, 2018

same for me. service looks like running, but no client can connect. user- or elevated level of command line.

G508031@RMM-P7000032FW MINGW64 /
$ net start com.docker.service
The Docker for Windows Service service is starting.
The Docker for Windows Service service was started successfully.

G508031@RMM-P7000032FW MINGW64 /
$ docker version
Client:
Version: 17.12.0-ce
API version: 1.35
Go version: go1.9.2
Git commit: c97c6d6
Built: Wed Dec 27 20:05:22 2017
OS/Arch: windows/amd64
error during connect: Get http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.35/version: 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.

G508031@RMM-P7000032FW MINGW64 /
$ net start com.docker.service
The requested service has already been started.

shaneasullivan commented Mar 14, 2018

I had the same issue — I was able to resolve the issue by running power shell with Admin privs. I validated this was the same behavior for running the commands via elevated cmd prompt. It also enabled docker run hello-world command which was returning the error message . Access is denied. 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.

heidricha commented Mar 15, 2018

Solved for me. Run docker desktop app, check in notification. Setup if necessary.
Be happy.

rn commented Apr 30, 2018

Closing this issue. @Venkateshkuntla, if you still have the problem, please re-open and supply a diagnostics ID and detaisl of your setup (Docker for Windows version etc).

girishgodage commented Jul 18, 2018

I had the same issue — I was able to resolve the issue by running power shell with Admin privs.

error during connect Get https://192.168.99.100:2376/v1.38/containers/json #2596

Comments

Foadsf commented Sep 12, 2018 •

I have tried with the latest version of my channel (Stable or Edge)

I have uploaded Diagnostics
log.txt

Diagnostics ID: 4751922A-3186-4B60-BD14-950E40145369/20180912112345

Expected behavior

When running docker container ls to get a list of containers.

Actual behavior

getting the error message:

error during connect: Get https://192.168.99.100:2376/v1.38/containers/json: dial tcp 192.168.99.100:2376: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.

Information

• Windows Version: Windows 10 Enterprise
• Docker for Windows Version: Version 18.06.1-ce-win73 (19507), Channel: stable, b0f14f1

Steps to reproduce the behavior

1. open terminal
2. run docker container ls

P.S. Guys, I do appreciate your efforts. But I have never been able to touch docker without spending hours to fix errors and issues. I think the whole docker structure is getting too cluttered. You need to spend more time fixing the common errors and be active on website like StackOverflow answering the questions and issues.

The text was updated successfully, but these errors were encountered:

Foadsf commented Sep 12, 2018 •

from here I ran the command in a admin cmd or powershell:

now the the docker container ls works but upon running Docker for Windows I get the error:

Hyper-V and Containers features are not enabled.
Do you want to enable them for Docker to be able to work properly?
Your computer will restart automatically.
Note: VirtualBox will no longer work.

and if I select cancel I get the error:

An error occurred
Required feature(s) not enabled : Hyper-V and Containers.
Docker will exit.

This is exhausting!

P.S. you might also need to run the command bcdedit /set hypervisorlaunchtype off in an admin powershell/cmd

Foadsf commented Sep 12, 2018

upon restart the error happened again. the way I solved it this time:

1. opened virtualbox and find the container where docker-machine or boot2docker (whatever it is. ) is named default
2. from here run docker-machine stop default and docker-machine start default
3. at this step you might get the error:

Error response from daemon: client version . is too new. Maximum supported API version is .

1. from here you may run docker-machine upgrade

these steps solved my problem for the moment.

Foadsf commented Sep 25, 2018

for those of you who end up here, do not install docker for windows. Install Docker ToolBox instead.

yamlCase commented Oct 14, 2018 •

for those of you who end up here, do not install docker for windows. Install Docker ToolBox instead.

Hi @Foadsf, can you sum up why not to use Docker for Windows and instead ToolBox? I’m apparently uninformed. Thanks!

atifmir commented Nov 17, 2018 •

@yamlCase Docker for windows is the best way to do it https://docs.docker.com/toolbox/toolbox_install_windows/ toolbox was for the legacy desktop.
Here is the solution that works, and there is no need to uninstall Oracle Virtual box hope this helps anyone else who experience this.
https://stackoverflow.com/questions/49679818/docker-could-not-read-ca-certificate

docker-desktop-robot commented Feb 15, 2019

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale comment.
Stale issues will be closed after an additional 30d of inactivity.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle stale

eugene-matvejev commented Apr 5, 2019

claudivanmoreira commented Apr 13, 2019 •

got same error using Docker For Windows:

error during connect: Get https://192.168.99.100:2376/v1.39/containers/json: dial tcp 192.168.99.100:2376: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.

Edition: Windows 10 Enterprise
Version: 1809
OS Build: 17763.437
Processor: Intel(R) Core(TM) i7-7820HQ CPU @ 2.90GHz
System type: 64-bit

shruti-rao commented Apr 24, 2019 •

Same error. /remove-lifecycle stale

$ docker version
Client:
Version: 18.03.0-ce
API version: 1.37
Go version: go1.9.4
Git commit: 0520e24302
Built: Fri Mar 23 08:31:36 2018
OS/Arch: windows/amd64
Experimental: false
Orchestrator: swarm
error during connect: Get https://192.168.99.100:2376/v1.37/version: dial tcp 19
2.168.99.100:2376: connectex: A connection attempt failed because the connected
party did not properly respond after a period of time, or established connection
failed because connected host has failed to respond.

scarabetta commented May 24, 2019

Same error here:

$ docker version
Client: Docker Engine — Community
Version: 18.09.2
API version: 1.39
Go version: go1.10.8
Git commit: 6247962
Built: Sun Feb 10 04:12:31 2019
OS/Arch: windows/amd64
Experimental: false
error during connect: Get https://192.168.99.100:2376/v1.39/version: dial tcp 192.168.99.100:2376: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.

marquish commented Jul 7, 2019

would you check ?
eval $(docker-machine env default)

please post > docker-machine env default result if not solved.

edward-objsec commented Jul 18, 2019 •

I am getting the same error, but only when shelling out from python (using subprocess.Popen) to execute docker commands. The ip in the error msg is as above: 192.168.99.100:2376. If I execute docker commands from a terminal they work as expected.

I have docker toolkit installed on a windows 10 machine. In the docker quickstart terminal the environment variable DOCKER_HOST=192.168.99.101:2376. I can ping 101, but pinging 100 errors with «TTL expired in transit.»

Thanks in advance for your help.

halmai commented Jul 26, 2019

I had the same error message after an unexpected power failure of the host computer.

After rebooting, I started VirtualBox and later on the Docker Toolbox. Then I get the same error message for the command docker images .

I deleted the virtual machine that the DockerTools installed for me and uninstalled the DockerTools too, then re-installed the same version. The problem was still the same.

Finally, I sent an ACPI shutdown to the VBox (Right click -> Close -> ACPI Shutdown) and exited from the Docker Toolbox too. Then, I did start only the Docker Toolbox and did not start the VBox. After a while, the Toolbox has started it automatically and it started to work fine.

I have no idea what exactly solved the problem but maybe it helps someone in the future.