This error may indicate that the docker daemon is not running что делать

asked Nov 7, 2016 at 6:46

The error is related to that part:

In the default daemon configuration on Windows, the docker client must
be run elevated to connect

• First, verify that Docker Desktop application is running. If not, launch it: that will run the docker daemon (just wait few minutes).

• Then, if the error still persist, you can try to switch Docker daemon type, as explained below:

With Powershell:

1. Open Powershell as administrator
2. Launch command: & 'C:Program FilesDockerDockerDockerCli.exe' -SwitchDaemon

OR, with cmd:

1. Open cmd as administrator
2. Launch command: "C:Program FilesDockerDockerDockerCli.exe" -SwitchDaemon

answered Apr 6, 2020 at 15:00

I had the same problem.

Starting the docker daemon resolved the issue. Just search for docker pressing windows key and click on «Docker Dekstop». Daemon should be running in a minute.

After starting up Docker Desktop, make sure the docker daemon status in the bottom left is green and shows RUNNING when you hover over it.

Error Code:

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

Solutions:

1) For Windows 7 Command Window(cmd.exe), open cmd.exe with run as administrator and execute following command:

docker-machine env --shell cmd default

You will receive following output:

SET DOCKER_TLS_VERIFY=1
SET DOCKER_HOST=tcp://192.168.99.100:2376
SET DOCKER_CERT_PATH=C:UsersUSER_NAME.dockermachinemachinesdefault
SET DOCKER_MACHINE_NAME=default
SET COMPOSE_CONVERT_WINDOWS_PATHS=true
REM Run this command to configure your shell:
REM @FOR /f "tokens=*" %i IN ('docker-machine env --shell cmd default') DO @%i

Copy the command below and execute on cmd:

@FOR /f "tokens=*" %i IN ('docker-machine env --shell cmd default') DO @%i

And then execute following command to control:

docker version

2) For Windows 7 Powershell, open powershell.exe with run as administrator and execute following command:

docker-machine env --shell=powershell | Invoke-Expression

And then execute following command to control:

docker version

3) If you reopen cmd or powershell, you should repeat the related steps again.

answered Jun 14, 2017 at 6:54

If you see docker desktop is STOPPED or Not Running screen at left side bottom, then do following

1. Open PowerShell with – Run as Administrator
2. Close Docker Desktop if it is open
3. Execute the following command on PowerShell
   “& 'C:Program FilesDockerDockerDockerCli.exe' -SwitchDaemon”
4. Open Docker Desktop, it will get started.

I was facing this issue. I tried the above-mentioned steps and it worked for me. Thanks!

I know this question was long ago but I found no proper explanation and solution, so hopefully, my answer is useful

Assuming you install Docker Toolbox on Windows, both docker and docker-machine commands will be available. Often, people get confused when to use either of these.

The docker commands are used only within a virtual machine to manage images. The docker-machine commands are used on the host to manage the Linux VMs.

So, please use docker-machine commands on your Windows machine. Use docker command inside your VM. To use the docker commands, for example, docker ps, you either can open Docker Quickstart Terminal or run these on your cmd/bash/PowerShell:

docker-machine run default /assuming default is your Linux VM/

docker-machine ssh default

This will start boot2docker and you will see the docker icon on the command line. Then you can use docker commands.

Good luck

answered Mar 1, 2018 at 1:34

Try resolving the issue with either of the following options:

Option A

Start-Service "Hyper-V Virtual Machine Management"
Start-Service "Hyper-V Host Compute Service"

or

Option B

1. Open «Window Security»

2. Open «App & Browser control»

3. Click «Exploit protection settings» at the bottom

4. Switch to «Program settings» tab

5. Locate «C:WINDOWSSystem32vmcompute.exe» in the list and expand it

6. Click «Edit»

7. Scroll down to «Code flow guard (CFG)» and uncheck «Override system settings»

8. Start vmcompute from powershell «net start vmcompute»

9. Then restart your system

I got the same error for Docker version 19.03.12 and Windows 10. Resolved it by going through the below steps. Hope it helps others.

1. Go to Windows Start -> Search Box (Type here to search). There
   enter ‘Services‘. Among the listed items, click Services app.
2. Now search ‘Docker Desktop Service‘ in the Services window opened. Right click on it and Start the service. Its status should be changed to ‘Running‘.
3. If step 2 gives error like ‘the dependency service failed to start‘, then start all dependency services. For me, I had to start a service called ‘Server‘.
4. Double click ‘Docker Desktop‘ icon in desktop. Now you will see ‘Docker Desktop is running‘ in system tray.
5. Now run the command ‘docker version‘ from Command Prompt or PowerShell. It should give clean output.
6. If any issue in step 5, run Command Prompt or PowerShell as administrator.

Above resolution assumes Docker is already installed and Hyper-V / Virtualization is enabled in your system.

answered Sep 4, 2020 at 16:33

ayunami2000ayunami2000

4215 silver badges10 bronze badges

I have faced same issue, it may be issue of administrator, so followed below steps to setup docker on

windows10

.

1. Download docker desktop from docker hub after login to docker.Docker Desktop Installer.exe file will be downloaded.
2. Install Docker Desktop Installer.exeusing Run as administrator -> Mark windows container during installation else it will only install linux container. It will ask for Logout after logging out and login it shows docker desktop in menu.
3. After install, go to -> computer management -> Local users and groups -> Groups -> docker-user -> Add user in members
   
4. Run docker desktop using Run as administrator
   
5. Check docker whale icon in Notification tab
   
6. run command >docker version
   
   Successfully using docker without any issue.

answered Nov 27, 2019 at 7:03

I had the same issue in the terminal right after installation of Docker Desktop 4.7.1 running with WSL 2 backend. The tray whale icon was not showing either.

In my case the problem was that I already had a WSL distribution (Ubuntu) installed before and it has been the default. Docker Desktop with WSL 2 backend installs its own distribution called docker-desktop. And it has to be the default one (at least if not configured elsewhere).

So I had to run this command in PowerShell: wsl --setdefault docker-desktop and restart docker services. Found the solution here.

answered Apr 30, 2022 at 14:43

RahulGRahulG

1,0281 gold badge15 silver badges27 bronze badges

If you have installed docker on Windows 10 Pro with Hyper-V enabled and you are still not able to run Docker on Windows 10, then, as the error suggests, your docker daemon is not started.

The following steps helped me to start docker successfully:

1. Use command on cmd(Admin mode)

   docker-machine restart default
   

2. Then you’ll get a message something like:

   open C:User\{User_name}\.dockermachinemachinesdefaultconfig.json:
   The system cannot find the file specified.

3. Go to the docker icon which will be on your windows tray (bottom right corner of the desktop)

4. Right click on the docker icon > Settings > Reset > Restart Docker

   It will take few moments

5. Then you’ll see the following message:

   Docker is running with the green indicator

Note: If you already had Docker containers running on your system, then don’t follow these steps. You may lose the existing containers.

Reason : one reason may cause because we shut down the vmmem by command

wsl --shutdown

Solution : Simple Restart the Docker by right-clicking will fix the problem.

answered Mar 23, 2021 at 9:01

answered Apr 9, 2021 at 4:57

Prasanth LouisPrasanth Louis

4,3992 gold badges31 silver badges47 bronze badges

I was getting same errors after an install on Windows 10. And I tried restarting but it did not work, so I did the following (do not recommend if you have been working in docker for awhile, this was on a fresh install):

1) Find the whale in your system tray, and right click

2) Go to settings > Reset

3) Reset to factory defaults

I was then able to follow the starting docker tutorial on the website with Windows 10, and now it works like a charm.

answered Jun 8, 2018 at 0:12

Open C drive in powershell Or Git bash and run below command

.Program FilesDockerDockerDockerCli.exe -SwitchDaemon

answered May 26, 2020 at 7:21

briancoderbriancoder

1591 silver badge8 bronze badges

answered Jun 28, 2018 at 12:55

olisteadmanolisteadman

4366 silver badges12 bronze badges

DaveDave

696 bronze badges

After installing docker desktop into your pc (windows one). You may find up this location. What is actually does,? It starts the Docker Daemon via your CLI

"C:Program FilesDockerDockerDockerCli.exe" -SwitchDaemon

Brookie_CBrookie_C

3691 silver badge10 bronze badges

That’s worked for me on win10-home https://github.com/docker/for-win/issues/11967

1. Shutdown your service docker
2. Now execute this into the window command terminal
   RMDIR /S %USERPROFILE%AppDataRoamingDocker
3. Startup your service docker
4. Now click on your «Docker Desktop»

The «Docker Desktop» will now runnig … done …

answered Oct 27, 2021 at 21:24

KarobweKarobwe

1961 silver badge5 bronze badges

Run this as Administrator

I tried that option too. You mean docker/ PowerShell

Yes, but try also cmd. Like dockerd in powershell and docker in cmd. And stop the service when you start with that.

Same issue happening to me. Tried different options and doesn’t solve it :

• Option 1 : Run through PowerShell with and without admin elevation
• Option 2 : Run it through cmd

Ok what says dockerd? When your runn it in powershell (Do you have the nat interface, do you stop the service….)??

Hi, I solved this running the docker for windows (dekstop app), as administrator (not the docker command)
like this:

hope it helps!
(was working fine, don’t what caused this, update?)

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

I had to go through this problem.
I was able to resolve this by switching the docket daemon.
cd «C:Program FilesDockerDocker»
./DockerCli.exe -SwitchDaemon

The solution was posted in (#1825).

Hi, I solved this running the docker for windows (dekstop app), as administrator (not the docker command)
like this:

hope it helps!
(was working fine, don’t what caused this, update?)

Worked for me (after restarting, logging in, and generally jumping through several hoops
Tx!

mofcomp.exe C:WindowsSystem32wbemNetNat.mof

worked for me!

@Ankit3794 getting the below error while running the above command

Microsoft (R) MOF Compiler Version 10.0.18362.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: C:WindowsSystem32wbemNetNat.mof
MOF file has been successfully parsed
Storing data in the repository...
An error occurred while processing item 1 defined on lines 5 - 12 in file C:WindowsSystem32wbemNetNat.mof:
Error Number: 0x80041003, Facility: WMI
Description: Access denied
Compiler returned error 0x80041003

Closed issues are locked after 30 days of inactivity.
This helps our team focus on active issues.

If you have found a problem that seems similar to this, please open a new issue.

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