Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
Venkateshkuntla opened this issue Mar 13, 2018 · 52 comments

Comments

@Venkateshkuntla
Copy link

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

  1. ...
  2. ...
@heidricha

This comment has been minimized.

Copy link

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

This comment has been minimized.

Copy link

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

This comment has been minimized.

Copy link

commented Mar 15, 2018

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

@rn

This comment has been minimized.

Copy link
Contributor

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).

@rn rn closed this Apr 30, 2018

@girishgodage

This comment has been minimized.

Copy link

commented Jul 18, 2018

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

@rorygilfillan

This comment has been minimized.

Copy link

commented Aug 3, 2018

I have the same issue since I upgraded. Powershell in admin mode doesn't help.

PS C:\WINDOWS\system32> docker version
Client:
Version: 18.06.0-ce
API version: 1.38
Go version: go1.10.3
Git commit: 0ffa825
Built: Wed Jul 18 19:05:28 2018
OS/Arch: windows/amd64
Experimental: false
error during connect: Get http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.38/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.

@mlenser

This comment has been minimized.

Copy link

commented Aug 28, 2018

Same issue as @rorygilfillan. Docker is on my PATH, but I get:
error during connect: Get http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.38/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.

@changshihkai0121

This comment has been minimized.

Copy link

commented Aug 31, 2018

same problem at my windows....

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

$ docker version
Client:
Version: 18.06.1-ce
API version: 1.38
Go version: go1.10.3
Git commit: e68fc7a
Built: Tue Aug 21 17:21:34 2018
OS/Arch: windows/amd64
Experimental: false
error during connect: Get http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.38/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.

@fluggo

This comment has been minimized.

Copy link

commented Sep 1, 2018

Same issue. Diagnostics ID 67ED6A1F-C0B5-466D-9BC3-DF0228895023/20180901135537

@Relaxe111

This comment has been minimized.

Copy link

commented Sep 11, 2018

same issue:
Version: 18.06.1-ce
API version: 1.38
Go version: go1.10.3
Git commit: e68fc7a
Built: Tue Aug 21 17:21:34 2018
OS/Arch: windows/amd64
Experimental: false
error during connect: Get http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.38/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.

@AlexEJerome

This comment has been minimized.

Copy link

commented Sep 17, 2018

Same issue: 601A73D6-300C-4099-96C4-1D1FE8D18493/20180917131950

@ducquoc

This comment has been minimized.

Copy link

commented Sep 25, 2018

I fixed this issue by settings the certificate environment variables (for SSH/TLS):

SET DOCKER_CERT_PATH=%UserProfile%\.docker\machine\machines\HypervDefault
SET DOCKER_MACHINE_NAME=HypervDefault
SET DOCKER_HOST=tcp://192.168.1.15:2376
SET DOCKER_TLS_VERIFY=1

The problem began when I created the "HypervDefault" machine, and deleted the "default" machine, which can be verified with docker-machine commands:

docker-machine ls
docker-machine env HypervDefault
FOR /f "tokens=*" %i IN ('docker-machine env HypervDefault') DO @%i

The above commands might need to run with Admin privileges (elevated), and make sure docker service is running: net start com.docker.service . Then the docker commands can run well:

docker ps
docker image ls
docker container ls --all

P.S: If your local IP Address (NAT) changes, for example: 192.168.1.3 --> 192.168.1.15 ; you can re-generate the certs (and it will auto update config.json for the machine respectively)
docker-machine regenerate-certs [machine-name]

-Duc

@blueyestar

This comment has been minimized.

Copy link

commented Oct 19, 2018

@ducquoc does not work at step FOR /f "tokens=*" %i IN ('docker-machine env HypervDefault') DO @%i

Windows 10 Home/ AMD64

@ducquoc

This comment has been minimized.

Copy link

commented Oct 22, 2018

@blueyestar :
That line, I use the "HypervDefault" as the machine name. In default case , the name is "default" . I think you should check that. (and adjust the variable environment to default respectively)

Another possibility is that some batch syntax (of cmd.exe) might not be run by PowerShell. In new versions of Docker they will use PowerShell syntax , so I think you can check the actual to be used by using the default (no machine name):

docker-machine env 

That will have output as a hint about the loop command to set environment variables. (though usually it's only the IP change need to be updated)

@zilurrane

This comment has been minimized.

Copy link

commented Oct 28, 2018

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

In Powershell elevated access solved my issue.

@prabuddha93

This comment has been minimized.

Copy link

commented Oct 30, 2018

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

In Powershell elevated access solved my issue.

Thanks!

@ManikantaCV

This comment has been minimized.

Copy link

commented Nov 21, 2018

@prabuddha93: Issue solved with your solution. Thank you

@mikfaina

This comment has been minimized.

Copy link

commented Nov 22, 2018

Me too

@alkreddy

This comment has been minimized.

Copy link

commented Nov 26, 2018

@zilurrane ...your tip resolved the issue... See my note for my observation

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

Especially on windows machine when you see the above error after a docker update, try the above commands. It appears like the Docker Desktop UI may indicate that you are already using Linux Containers, but the update may have messed up that setting. Running the above commands will set to Linux Containers and there after you can work happily.

@bhanotra

This comment has been minimized.

Copy link

commented Dec 4, 2018

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

In Powershell elevated access solved my issue.

worked for me as well

@eduuh

This comment has been minimized.

Copy link

commented Dec 6, 2018

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

this worked for me..Thank you very much

@naywin-programmer

This comment has been minimized.

Copy link

commented Dec 7, 2018

open with powershell, It work for me.

@ngie-eign

This comment has been minimized.

Copy link

commented Dec 10, 2018

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

In Powershell elevated access solved my issue.

Thanks!

This isn't a workable solution to be honest for Linux containers users (assuming Docker is configured to use Linux containers), since it papers over an issue with Linux Containers by switching Docker over to use Windows containers.

There's a problem with the interoperability of Docker, HyperV, Linux containers, and security levels (in my case) that are preventing me from making progress installing even the most basic docker containers (alpine, centos).

I'm going to look around a bit more for instructions, and if all else fails, screw it and install a Linux desktop on my corporate laptop in order to get my job done. I've been very disappointed with how much of a headache it's been trying to get this to work on Windows, compared to OSX where everything "just worked out of the box".

@ngie-eign

This comment has been minimized.

Copy link

commented Dec 10, 2018

For anyone else reading this thread, the error message is coming from HyperV.

@taishjason

This comment has been minimized.

Copy link

commented Dec 19, 2018

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

In Powershell elevated access solved my issue.

Thanks for this. It solve my issue.

@ngie-eign

This comment has been minimized.

Copy link

commented Dec 19, 2018

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

In Powershell elevated access solved my issue.

Thanks for this. It solve my issue.

As noted previously, this switches Docker from Linux to Windows containers. This doesn't likely fix the underlying issue; it only papers over the fact that there's an issue with HyperV interacting with Docker.

I'll see if I can get Docker to work with my Windows 10 Pro desktop, given that I no longer have access to the machine that I ran into the original issues with.

@StudioDove

This comment has been minimized.

Copy link

commented Dec 29, 2018

I had the same issue very recently and was able to get it working again pretty easily:

`Client: Docker Engine - Community
Version: 18.09.0
API version: 1.39
Go version: go1.10.4
Git commit: 4d60db4
Built: Wed Nov 7 00:47:51 2018
OS/Arch: windows/amd64
Experimental: false

Server: Docker Engine - Community
Engine:
Version: 18.09.0
API version: 1.39 (minimum version 1.12)
Go version: go1.10.4
Git commit: 4d60db4
Built: Wed Nov 7 00:55:00 2018
OS/Arch: linux/amd64
Experimental: false
`

I fixed it by using "Reset to factory defaults..." under Settings > Reset.

Of course I had to sign in again and all my containers were gone, so I had to re-download everything but that's not a big deal, after all that is what docker is for, right!

@yasemindogan93

This comment has been minimized.

Copy link

commented Jan 17, 2019

Solved:

  • Go to Docker-Icon -- >right click and select settings.
  • activating "expose daemon on tcp://...without tls".
  • check in powershell by simple 'docker ps'
@jorbensaaltink

This comment has been minimized.

Copy link

commented Jan 18, 2019

Switch from Windows containers to Linux containers. Works for me ;)

@yasemindogan93

This comment has been minimized.

Copy link

commented Jan 18, 2019

Seems there are several reasons after docket updates on windows.
Should be more consistent.

@yoesak

This comment has been minimized.

Copy link

commented Jan 20, 2019

I also get this error message,

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

only switch from Linux Container to Windows Container,

But in my case, the problem was somehow the permission to the 'C:\ProgramData\Docker\config\daemon.json' is missing, so the docker cannot read the configuration file, by granted the 'CREATOR OWNER' user to access the file, the problem gone

@fjgodino

This comment has been minimized.

Copy link

commented Jan 25, 2019

I resolved with docker logout

@adinunzio84

This comment has been minimized.

Copy link

commented Feb 13, 2019

Same issue, and like @ngie-eign we need to use Linux containers. Anyone find a solution for Linux containers on Windows with hyper-v?

@levdikpavel

This comment has been minimized.

Copy link

commented Feb 21, 2019

Had the same issue

I just run "DockerCli.exe -SwitchDaemon" twice, to switch back to Linux containers, and the error has gone, and I got back my 270 images, now I am happy

@olavorn

This comment has been minimized.

Copy link

commented Feb 22, 2019

For me, this issue happened in My Windows 10 Pro when it recovered from a hibernation.

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

Didn't solve cause daemon was already started. So there was an access denied error.

I suspect if the DockerCli already running, you can set and unset "Expose daemon on tcp:..."
image

That worked for me.

@ngie-eign

This comment has been minimized.

Copy link

commented Feb 22, 2019

@olavorn: that exposes the docker daemon over unencrypted TLS, which is obviously insecure. Check the firewall and permissions for the daemon.

@olavorn

This comment has been minimized.

Copy link

commented Feb 22, 2019

@ngie-eign: That's why i mentioned "set and unset" ;)

@RatanGithub

This comment has been minimized.

Copy link

commented Mar 27, 2019

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

In Powershell elevated access solved my issue.

This resolved the issue

@pengfeidip

This comment has been minimized.

Copy link

commented Apr 6, 2019

Solved:

  • Go to Docker-Icon -- >right click and select settings.
  • activating "expose daemon on tcp://...without tls".
  • check in powershell by simple 'docker ps'

@yasemindogan93 win10 pro , useful!

@Baharul1

This comment has been minimized.

Copy link

commented Apr 7, 2019

Hi ,

I am also getting same error. I am have tried with AWS & Azure VM . Also have tried with windows powershell , but still getting same error always. At system initial start-up got error as

`nable to start: The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: 'MobyLinuxVM' failed to start.

Failed to start the virtual machine 'MobyLinuxVM' because one of the Hyper-V components is not running.

'MobyLinuxVM' failed to start. (Virtual machine ID D7E5B883-BE98-4021-A331-205E40628A28)

The Virtual Machine Management Service failed to start the virtual machine 'MobyLinuxVM' because one of the Hyper-V components is not running (Virtual machine ID D7E5B883-BE98-4021-A331-205E40628A28).
at Start-MobyLinuxVM, : line 296
at , : line 412
at Docker.Core.Pipe.NamedPipeClient.Send(String action, Object[] parameters) in C:\workspaces\stable-18.09.x\src\github.com\docker\pinata\win\src\Docker.Core\pipe\NamedPipeClient.cs:line 36
at Docker.Actions.DoStart(SynchronizationContext syncCtx, Boolean showWelcomeWindow, Boolean executeAfterStartCleanup) in C:\workspaces\stable-18.09.x\src\github.com\docker\pinata\win\src\Docker.Windows\Actions.cs:line 92
at Docker.Actions.<>c__DisplayClass19_0.b__0() in C:\workspaces\stable-18.09.x\src\github.com\docker\pinata\win\src\Docker.Windows\Actions.cs:line 74
at Docker.WPF.TaskQueue.<>c__DisplayClass19_0.<.ctor>b__1() in C:\workspaces\stable-18.09.x\src\github.com\docker\pinata\win\src\Docker.WPF\TaskQueue.cs:line 59`

@mchudinov

This comment has been minimized.

Copy link

commented Apr 9, 2019

This issue happens to me daily. So I need to switch to Windows and then back to Linux at least once every day to make Docker works.
Docker version 18.09.2
Windows 10 Pro
Docker system tray does not work at all anymore.

docker info Containers: 3 Running: 3 Paused: 0 Stopped: 0 Images: 7 Server Version: 18.09.2 Storage Driver: overlay2 Backing Filesystem: extfs Supports d_type: true Native Overlay Diff: true Logging Driver: json-file Cgroup Driver: cgroupfs Plugins: Volume: local Network: bridge host ipvlan macvlan null overlay Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog Swarm: inactive Runtimes: runc Default Runtime: runc Init Binary: docker-init containerd version: 9754871865f7fe2f4e74d43e2fc7ccd237edcbce runc version: 09c8266bf2fcf9519a651b04ae54c967b9ab86ec init version: fec3683 Security Options: seccomp Profile: default Kernel Version: 4.9.125-linuxkit Operating System: Docker Desktop OSType: linux Architecture: x86_64 CPUs: 2 Total Memory: 1.934GiB Name: docker-desktop ID: 7EFR:JHW4:U5KU:2P45:XFH5:JJG7:MA2K:QSTU:4LME:Q2P6:LZZG:EQBR Docker Root Dir: /var/lib/docker Debug Mode (client): false Debug Mode (server): true File Descriptors: 22 Goroutines: 48 System Time: 2019-04-09T13:37:04.5084016Z EventsListeners: 1 Registry: https://index.docker.io/v1/ Labels: Experimental: true Insecure Registries: 127.0.0.0/8 Live Restore Enabled: false Product License: Community Engine

@sleepyhollo

This comment has been minimized.

Copy link

commented Apr 9, 2019

I was stuck on something like this. Try this fix (original source). My problem was with Hyper-V not starting up, and that fixed it for me.

@ngie-eign Maybe this works for you too

@thiagosrios

This comment has been minimized.

Copy link

commented Apr 23, 2019

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

In Powershell elevated access solved my issue.

This solved for me. Thanks!!

@erzhu4

This comment has been minimized.

Copy link

commented May 1, 2019

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

In Powershell elevated access solved my issue.

OMG You are a life saver!!!!

@olisteadman

This comment has been minimized.

Copy link

commented May 22, 2019

For me the error was resolved by stopping a virtual Ubuntu instance that'd been running in Hyper-V:

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.

Once Ubuntu instance had been stopped, and Docker Desktop had been restarted, my usual docker commands ran just fine.

PS: I had the idea to try this because of an Error Log that Docker Desktop had helpfully compiled and offered to send to Docker Hub as user feedback... the log appeared to indicate that my machine was short on RAM, and Docker was failing for this very simple reason. Killing the Ubuntu instance solved that.

@tschach

This comment has been minimized.

Copy link

commented Jun 7, 2019

I solved this issue by switching from executing docker pull ... in powershell to executing it in cmd. Elevated powershell did not work for me, I did not try the other solutions.

@sammy111286

This comment has been minimized.

Copy link

commented Jul 8, 2019

I faced the same issue . I tried the elevated powershell but it was of no use . So I tried restarting the system , but still it didn't work for a few minutes. The thing was , it takes some time to bring up the docker sometimes even when the docker icon in the taskbar is stable . Once it is stable you can execute "net start com.docker.service" on the powershell . It would generate the message - "The requested service has already been started." if it is already up. and then try the docker commands.

@ank2311

This comment has been minimized.

Copy link

commented Jul 11, 2019

Please help with docker Diagonse ID : 7313DB8A-55BD-4221-81CE-61FCF9C43151/20190711154240

Error during connect.
Please assist.

@PatOShea

This comment has been minimized.

Copy link

commented Jul 16, 2019

I got this when trying to pull from my own registry. Once I logged in the pull worked fine:

  • docker login URL:port
    (prompts for login credentials)
  • docker pull URL:port/path <- successful this time

@ThaoThanhLuu ThaoThanhLuu referenced this issue Jul 23, 2019

Open

Not able to start docker #4173

0 of 2 tasks complete
@niemyjski

This comment has been minimized.

Copy link

commented Jul 30, 2019

The powershell tip helped me but then I got ERROR: client version 1.22 is too old. Minimum supported API version is 1.24, please upgrade your client to a newer version

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
You can’t perform that action at this time.