Docker desktop for windows 10 не запускается

I habe the same problem, since some days:

• Windows Version: Windows 10 Pro 20H2 — Build 19042.928
• Docker Desktop Version: 3.3.1
• WSL2 or Hyper-V backend? WSL 2 based engine
• Are you running inside a virtualized Windows e.g. on a cloud server or a VM: No
• Diagnostics ID: 60E75FB0-7B8D-4333-83B1-B75108000EBD/20210419044416

The first days restarting the com.docker.service service fixes this issue. But now I must go to the Troubleshooting menu in Docker Desktop an «Clean / Purge data» for WSL2. After that, Docker works again, but only until the next restart.

I tried to reinstall WSL2 and also turn off fast startup in Windows, but this does not solve the problem.

The output of «wsl -l -v» after a restart is:

  NAME                   STATE           VERSION
* Ubuntu                 Running         2
  docker-desktop-data    Stopped         2
  docker-desktop         Stopped         2

The docker icon in the taskbar not showing «the small container».

Same here

Windows Version: Windows 10 Pro 10.0.19041 Build 19041
Docker Desktop Version: 3.3.1
WSL2 or Hyper-V backend: WSL 2 based engine
Are you running inside a virtualized Windows e.g. on a cloud server or a VM: No

Similar to Abrueck. When I clean/purge data the WSL2 engine starts and everything seems to work again.

Same thing for me since 3.3.1 using Hyper-V. Cleaning data also solve the issue.

Here is my Diagnostics ID if it can help: 1D7DFA7F-F9AD-4393-9DEE-920993A35CC7/20210420110952

I had the same problems with 3.3.1 using WSL2.

Downgrading to 3.2.2, Reset to factory defaults and updating to 3.3.1 fixed it for me.

@CPTechnikVX Is it fixed permanently? The same procedure worked for me, but only until I rebooted the computer. Now, when I try to start Docker it hangs again. I then have to go back and reset to factory or purge, before I can start Docker

@CPTechnikVX Is it fixed permanently? The same procedure worked for me, but only until I rebooted the computer. Now, when I try to start Docker it hangs again. I then have to go back and reset to factory or purge, before I can start Docker

@chlillelund Unfortunately, I have the same behaviour. After a reboot it’s broken again and I can’t reach «Troubleshoot» anymore But that happened only after I started using kubernetes again. No idea if there is a connection.

It seems to be an issue with WSL2. I had to disable from Windows Features, uninstall docker, restart, install docker again but at the moment it asks to deploy WSL2 I unchecked this and it worked. So I can confirm there is an issue with WSL2 and docker desktop for Windows. Do you know guys who should to report this bug?

I tried adding the following lines to my .wslconfig file

[wsl2]
guiapplications=false

but Docker started successfully only once. I don’t think the changes made it work once. The proposal does not seem to solve my problem.

I am one step further. I found out that Docker only starts for me when I am connected to the company via VPN (domain controller?). I have disabled autostart, connect via VPN first after login and then start Docker. With version 3.2.x it still ran without VPN. No idea if that helps narrow down the cause.

Same issue for me, even downgrading to 3.3.0 didn’t help.
Even if Docker Desktop starts up, at some point after that it will lose the connection somehow and is not able to restore it. I then have to purge all data and redeploy all containers and hope they work as expected. (all HpyerV Backend, no WSL whatsoever)

Diagnostic ID 9128567D-5F64-415B-AEC3-AC20E97D3825/20210422134148

Also; when this happens and I run docker container ls e.g. from CMD it shows Error reponse from Daemon: i/o timeout

I found the following line in the log which confuses me. I have neither WSL2 installed nor have I checked the «use WSL2» checkbox in docker.

Why is it trying to use it?

[15:49:36.484][GoBackendProcess  ][Info   ] GET failed with Get "http://unix/forwards/list": open \.pipedockerWsl2BootstrapExposePorts: Das System kann die angegebene Datei nicht finden.

Edit; I got it running after some purges and what I noticed is in the log the following lines are just repeating every couple of seconds. As I said, I don’t use WSL2 and I do not have any VPN connections on the machine.

[16:26:36.658][GoBackendProcess  ][Info   ] GET failed with Get "http://unix/forwards/list": open \.pipedockerWsl2BootstrapExposePorts: Das System kann die angegebene Datei nicht finden.
[16:26:36.658][GoBackendProcess  ][Info   ] msg="external: GET /forwards/list 200 "Go-http-client/1.1" """
[16:26:36.658][ApiProxy          ][Info   ] msg="proxy << GET /v1.40/containers/json?all=true (2.8309ms)n"
[16:26:36.659][ApiProxy          ][Info   ] msg="proxy >> GET /v1.40/images/jsonn"
[16:26:36.659][VpnKitBridge      ][Info   ] msg="error CloseWrite to: Die Pipe wird gerade geschlossen."
[16:26:36.662][ApiProxy          ][Info   ] msg="proxy << GET /v1.40/images/json (1.619ms)n"
[16:26:36.662][VpnKitBridge      ][Info   ] msg="error CloseWrite to: Die Pipe wird gerade geschlossen."
[16:26:36.670][ApiProxy          ][Info   ] msg="proxy >> GET /v1.40/containers/json?all=truen"

I am one step further. I found out that Docker only starts for me when I am connected to the company via VPN (domain controller?). I have disabled autostart, connect via VPN first after login and then start Docker. With version 3.2.x it still ran without VPN. No idea if that helps narrow down the cause.

As @CPTechnikVX indicated above, I too have found that if I connect to my company’s VPN first, then Docker Desktop will start and appears to run normally. I can also confirm that version 3.2.x started and ran fine without the VPN being connected. Because I’m not on a team version, when 3.2.x is installed, it is automatically upgraded to 3.3.1 on the next reboot and the problem comes right back.

Also, when not connected to the VPN, the Docker Desktop (3.3.1) Settings Screen has a spinner on it that loads forever.

The support/diagnostics screen is able to load and I was able to register a successful diagnostic. This is in the «broken» mode where I’m not connected to the VPN and docker desktop will not successfully load:
Diagnostics ID: D02CCEDE-9F66-403C-8750-365AE8E7959B/20210422135409

Hope this helps.

I’m having the same issue. Version 3.2.2 will start and keep running, but I can’t stop it from updating to a higher version.
3.3.0 and higher will only start (even immediately after a complete re-install) after resetting to factory settings. After any restart it fails again.
I’m also getting the error during connect: In the default daemon configuration on Windows, the docker client must be run with elevated privileges to connect.: Get http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.24/containers/json: open //./pipe/docker_engine: The system cannot find the file specified. error from the cli.

From what I can tell there are two background processes that aren’t starting: com.docker.proxy.exe and com.docker.wsl-distro-proxy.exe. After resetting to factory defaults these start up and everything works as expected.

Diagnostics Id: 08966A9E-4F41-4FBC-B95C-F3F994876D15/20210422233159

@stevenobird

Restarting the Docker Desktop.exe and the com.docker.service service fixes this issue — until the next Windows reboot.

could you expand on this? I have restarted the Docker Desktop.exe and also restarted the service with pwsh admin Restart-Service com.docker.service but it doesn’t seem to fix the issue for me — though everything else seems exactly as you describe.

@stevenobird

Restarting the Docker Desktop.exe and the com.docker.service service fixes this issue — until the next Windows reboot.

could you expand on this? I have restarted the Docker Desktop.exe and also restarted the service with pwsh admin Restart-Service com.docker.service but it doesn’t seem to fix the issue for me — though everything else seems exactly as you describe.

That’s really the only two steps I do to temporarily fix the issue.
I stop Docker Desktop.exe with the Task Manager under «Details» tab and switch to «Services» tab to restart com.docker.service (which should be similar to doing it with Powershell). After that, I manually open up Docker Desktop.exe again and everything boots up as it should.

@stevenobird

Restarting the Docker Desktop.exe and the com.docker.service service fixes this issue — until the next Windows reboot.

could you expand on this? I have restarted the Docker Desktop.exe and also restarted the service with pwsh admin Restart-Service com.docker.service but it doesn’t seem to fix the issue for me — though everything else seems exactly as you describe.

That’s really the only two steps I do to temporarily fix the issue.

I stop Docker Desktop.exe with the Task Manager under «Details» tab and switch to «Services» tab to restart com.docker.service (which should be similar to doing it with Powershell). After that, I manually open up Docker Desktop.exe again and everything boots up as it should.

Hmm, that doesn’t seem to work for me but if I go into the troubleshooting part of the docker desktop app and purge hyperv data it forces a restart of the docker service and boots up again, keeping my wsl2 images etc because it’s using the WSL2 engine instead.

It could just be me not doing the Windows service restarts right etc, but it’s an easier workaround anyway tbh.

@stevenobird

Restarting the Docker Desktop.exe and the com.docker.service service fixes this issue — until the next Windows reboot.

could you expand on this? I have restarted the Docker Desktop.exe and also restarted the service with pwsh admin Restart-Service com.docker.service but it doesn’t seem to fix the issue for me — though everything else seems exactly as you describe.

That’s really the only two steps I do to temporarily fix the issue.

I stop Docker Desktop.exe with the Task Manager under «Details» tab and switch to «Services» tab to restart com.docker.service (which should be similar to doing it with Powershell). After that, I manually open up Docker Desktop.exe again and everything boots up as it should.

Hmm, that doesn’t seem to work for me but if I go into the troubleshooting part of the docker desktop app and purge hyperv data it forces a restart of the docker service and boots up again, keeping my wsl2 images etc because it’s using the WSL2 engine instead.

It could just be me not doing the Windows service restarts right etc, but it’s an easier workaround anyway tbh.

And there’s my problem: Docker Desktop is unresponsive/hanging so I can’t even get to the troubleshooting part. 😅 That’s why I take my described steps in the first place.

@stevenobird

Restarting the Docker Desktop.exe and the com.docker.service service fixes this issue — until the next Windows reboot.

could you expand on this? I have restarted the Docker Desktop.exe and also restarted the service with pwsh admin Restart-Service com.docker.service but it doesn’t seem to fix the issue for me — though everything else seems exactly as you describe.

That’s really the only two steps I do to temporarily fix the issue.
I stop Docker Desktop.exe with the Task Manager under «Details» tab and switch to «Services» tab to restart com.docker.service (which should be similar to doing it with Powershell). After that, I manually open up Docker Desktop.exe again and everything boots up as it should.

Hmm, that doesn’t seem to work for me but if I go into the troubleshooting part of the docker desktop app and purge hyperv data it forces a restart of the docker service and boots up again, keeping my wsl2 images etc because it’s using the WSL2 engine instead.
It could just be me not doing the Windows service restarts right etc, but it’s an easier workaround anyway tbh.

And there’s my problem: Docker Desktop is unresponsive/hanging so I can’t even get to the troubleshooting part. 😅 That’s why I take my described steps in the first place.

Ah interesting! For me, the docker desktop settings page hangs and is unresponsive, but I’m able to access the troubleshooting tab! I hope it’s fixed soon, I keep on ranting and raving to people at work at how good the WSL2 workflow is instead of virtualbox and then this happens 🤣

Ah interesting! For me, the docker desktop settings page hangs and is unresponsive, but I’m able to access the troubleshooting tab! I hope it’s fixed soon, I keep on ranting and raving to people at work at how good the WSL2 workflow is instead of virtualbox and then this happens 🤣

Got it working now. Double click on the icon in the taskbar makes it indeed working so I can finally send diagnostics that are in an «unresponsive» state.

Diagnostic ID: CEE7896D-A758-4E58-87F1-61F5D73B9549/20210423174133

What worked for me now (twice) is to sign out of Windows and then sign back in again.

I seem to have a similar problem. I need to purge all data to make Docker start again and be useable in WSL2 after a reboot. I am using version 3.3.1 of Docker Desktop. I upgraded a few weeks ago to 3.3.1 and had no issues so far. The problem appeared just a few days ago. The only thing that changed recently is, that I installed the KB4023057 Windows update. After that, the problem started to occur.

The solution «stop Docker Desktop.exe with the Task Manager under «Details» tab and switch to «Services» tab to restart com.docker.service » works for me, but I also noticed that if I wait several minutes after logging to my PC before starting docker desktop (I disabled automatic start) it works too (but then ,sometimes, docker takes 5 minutes to achieve start. It seemes relatated to com.docker.proxy.exe ) Docker for windows is a good product but at almost every update I encounter problems.

Same issue here. One time the server restarted in June, and Docker failed to start automatically for the reasons mentioned above. Manually starting Docker from services.msc later after restart works.

Another time happened just a few days ago. Same scenario.

I’m new to docker but been fighting this for weeks, quite honestly have never gotten it to run correctly. How is it something is so funded and popular but literally does not work in Windows at all after months of attempts? I ask with sincerity as this is rather perplexing why you all poor so much effort into running something that simply resists — to what benefit?

I’m new to docker but been fighting this for weeks, quite honestly have never gotten it to run correctly. How is it something is so funded and popular but literally does not work in Windows at all after months of attempts? I ask with sincerity as this is rather perplexing why you all poor so much effort into running something that simply resists — to what benefit?

The vast majority of time it just works in Windows. As such, it has become a core part of many workflows and other applications, and so when an individual does run into a problem, they often don’t have the option of just not using it.

Below steps resolved for me

1. Taskbar icons —> Right Click on Docker icon —> Click TroubleShoot from the context menu
2. Click — Clean/Purge Data button
3. Select all data sets — Hyper-V, WSL 2, Windows Contaienrs
4. Wait for cleanup to complete
5. Quit Docker desktop as : Taskbar icons —> Right Click on Docker icon —> Click Quit
6. Start Docker desktop again

Thanks, @josh9383
The above steps saved me after with windows11 upgrade.

Below steps resolved for me

1. Taskbar icons —> Right Click on Docker icon —> Click TroubleShoot from the context menu
2. Click — Clean/Purge Data button
3. Select all data sets — Hyper-V, WSL 2, Windows Contaienrs
4. Wait for cleanup to complete
5. Quit Docker desktop as : Taskbar icons —> Right Click on Docker icon —> Click Quit
6. Start Docker desktop again

Thanks, @josh9383 The above steps saved me after with windows11 upgrade.

You can go into troubleshoot directly from docker also . When I tried to purge the data it gave a prompt that I have to download and install WSL2 and gave a link where I could download that.
as the link was not clickable I typed the same in browser and opened it . It was of Microsoft download page of WSL 2 .
I downloaded and installed WSL2 and then reopened docker and was able to purge the data this time . After which I got the docker basic tutorial screen.

Same problem here. Windows starts, Docker doesn’t, no tray icon, nothing. Task manager shows Docker Desktop and Docker.Service running, with Docker Desktop Backend showing up for a fraction of a second ever few minutes. When I run Docker Desktop from the exe or the shortcut (even as Admin, still the same), I instantly get a window popup with «Docker failed to initialize The operation had timed out.» without any hanging or anything, just instant popup.

I’ve tried killing and restarting all the processes I can find, tried uninstall/reinstall, tried downgrading all the way back to 3.5.0, re-installed the Linux package, made sure Virtual Machine Platform and Windows Subsystem for Linux are both checked, checked bios to make sure all virtualizations are enabled.. Everything was working fine yesterday evening, wont work now. I also tried running docker commands from the cli but it says the daemon isn’t running. I tried to run it manually but «dockerd» isn’t a recognized command. Also tried «DockerCli.exe -SwitchDaemon» and that does nothing. Multiple, shutdowns, reboots and logouts also do nothing. I’m out of ideas at this point.

I got this too with Docker v4.0 & v4.1. I had to rollback/clean install v3.3.0, seems to be the only version working fine on my Windows 10 :'(

Here is what helped me with Docker Desktop 4.1.1 (69879) on Windows Pro 10

1. Make sure you have Instaled WSL 2 backend

Open powershell as administrator
Type as command

wsl.exe --install -d Ubuntu

Set Ubuntu version wsdl 2

wsl --set-version Ubuntu 2

Set wsl to as default version 2

wsl --set-default-version 2

1. Enable VirtualMachinePlatform

Open powershell as administrator
Type as command

Enable-WindowsOptionalFeature -Online -FeatureName VirtualMachinePlatform

1. Install Docker Docker Desktop (4.1.1)

2. Run Docker Desktop and make sure you have dockeker desktop settings

1. Restart

Man, I still never got this to work again, even after complete uninstall/reinstall, including purge data and manually delete AppData. Uninstalled again. Going to Rancher Desktop + nerdctl

What was working for me, after several re-installs:

1. Remove Docker Desktop from autostart
2. (Re-)Boot up Windows
3. Manually Stop Docker Desktop Service
4. Optionally connect to your VPN
5. Manually Start Docker Desktop Service
6. Start Docker Desktop
7. Wait for 30(!) Minutes
   => Docker Desktop is running

Still using Hyper V Backend, wsl2 has too many issues (https://github.com/Microsoft/WSL/issues). More occupied with repairing things in windows than actually developing.

Technical Masterpiece…
WSL2 Backend is crappy as hell, alone due to ext4 issues when your are shutting down your PC to fast (not that we have any control over that in Windows).
If I were not forced to develop on windows, I never would use this. Oh, wait, this costs money now? What for exactly?

Same here (since half a year or so). Having to restart WSL2 completely which forces docker to restart. Before that I can’t communicate with any container.

Hi All
Almost certainly a different issue but we were unable to get 4.5.0 to start on Windows 11 (we only tried Win 11)
We had to install 4.4.4 instead.

@dodgyd Hey experiencing the same issue.

@Tylerpfarris I saw that 4.5.1 is out now but I have held of updating from 4.4.4.
I have not had any issues with 4.4.4

My issue was docker would not start at all.

Hello All,

How I have fixed this issue is by ensuring that:

• The WSL 2 docker-engine was running inside of Ubuntu 20.04
• The docker daemon has been started.
• «Use the WSL 2 based engine» was checked in Docker Desktop.

After that, essentially restarting the docker desktop was all I needed to get my environment working again.

@dodgyd I had a similar problem. The tool stopped working after updating to version 4.5.1. Instead of downgrading to 4.4.4, I tried using the new version 4.6.0. It worked.

Same issue here with newest docker-desktop (4.6.1 (76265)). How i got it working again:

1. Close all docker-related processes via the task manager
2. Purge the settings.json file C:UsersUSERNAMEAppDataRoamingDocker
3. Startup Docker as normal user again

For me neither pre-configured containers nor their settings or data got lost.
Hope this helps you guys!

So….. If you’re upgrading, as I just did from an old Docker desktop from about 3-4 years ago and hit a brick wall — test if you were running Windows containers as it appears that this does something kooky with your Hyper-v and kinda sets it, and the upgrade wants to default to Linux containers which for me was throwing the error. When I switched to Windows containers the Docker started working (stopped and restarted ) — Hope that helps (Btw, now on: Docker version 20.10.14, build a224086)

Started my second attempt to upgrade Docker Desktop to the current version 4.7.1 and ran into the same issue once again. Docker won’t start, and none of the above fixes worked for me. The only solution was to revert to version 4.4.4 which works flawlessly.

Just for the record, in my case the file at %AppData%/Roaming/Docker/locked-directories was corrupt. Deleting it made Docker startup work again. The problem was mentioned in %AppData%/Roaming/Docker/log/hostcom.docker.backend.exe.log, it just took me a while to find this error message.

Purge the settings.json file C:UsersUSERNAMEAppDataRoamingDocker
CraignRush

removing settings.json worked for me.
even when running Docker desctop

Just for the record, in my case the file at %AppData%/Roaming/Docker/locked-directories was corrupt. Deleting it made Docker startup work again. The problem was mentioned in %AppData%/Roaming/Docker/log/hostcom.docker.backend.exe.log, it just took me a while to find this error message.

This worked for me

Purge the settings.json file C:UsersUSERNAMEAppDataRoamingDocker
CraignRush

removing settings.json worked for me. even when running Docker desctop

Same, I removed settings.json and locked-directories

Docker desktop is failing to start after upgrading to 4.9.1. I tried removing settings.json and locked-directories but nothing worked. Totally clueless as there is not relevant reason as why it is failing.

C:UsersUSERNAMEAppDataRoamingDocker
and delete settings.json file. start docker desktop again

C:UsersUSERNAMEAppDataRoamingDocker and delete settings.json file. start docker desktop again

As mentioned in my comment, it didn’t work. I upgraded to Docker Desktop 4.10.0 and it started working fine.

Started my second attempt to upgrade Docker Desktop to the current version 4.7.1 and ran into the same issue once again. Docker won’t start, and none of the above fixes worked for me. The only solution was to revert to version 4.4.4 which works flawlessly.

Upgraded to Docker Desktop 4.12.0 today and the application launches successfully. 🙌

This solved it for me.

#1825 (comment)

DockerCli.exe -SwitchDaemon

Did Docker start after you used this command ? Or did it take some time ? From what I’ve seen it takes between 30 min and 1 hour

I just downloaded it again and installed it on top of my current installation and it worked.

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

4235 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

asked Apr 27, 2016 at 9:39

Hyper-V and VirtualBox are conflicting each other.

You can either uninstall Hyper-V or run

docker-machine create -d virtualbox --virtualbox-no-vtx-check test

Source

answered Apr 27, 2016 at 9:49

Docker supports Hyper-V as the driver

You need to perform the following steps:

• Create a virtual switch, refer to this article on how to do that

• Create a docker machine using that network switch and hyper-V driver.

  docker-machine create -d hyperv --hyperv-virtual-switch "name of the virtual switch created above" default
  

I got the same error when I installed Docker Toolbox on my Windows 10 machine.

Solution:

1. Install Docker Community Edition (not Docker Toolbox)
2. Enable Hyper-V

Open Control Panel -> System and Security -> Programs (left panel) -> Turn Windows features on or off -> Check the Hyper-V box

As of 2017’s Win 10, if you don’t have Hyper-V option, then your Windows OS is not Enterprise Edition. Also, Docker seems to work a lot better on Intel processors (not AMD).

1. Add C:Program FilesDockerDockerresourcesbin to Path in Environmental Variables.
2. Open Git Bash and type docker-compose up and now that command should work.

If you don’t have GitBash, please download it.

I was having the same issue, and this blog post solved it. The author runs you through the steps of adding the --virtualbox-no-vtx-check flag to the docker shell script.

Virtualbox and Hyper-V don’t play well together. I am NOT the author.

answered Jun 28, 2016 at 21:58

answered Aug 25, 2017 at 9:09

See if when you run:

docker-machine create -d hyperv --hyperv-virtual-switch "Virtual Switch" default

you get Error with: pre-create check: "Hyper-V PowerShell Module is not available"

If so just enable in Docker(icon on your desktop)->settings->expose daemon on TCP …

answered May 28, 2020 at 15:12

ItharIthar

4,6154 gold badges38 silver badges38 bronze badges

asked Apr 27, 2016 at 9:39

Hyper-V and VirtualBox are conflicting each other.

You can either uninstall Hyper-V or run

docker-machine create -d virtualbox --virtualbox-no-vtx-check test

Source

answered Apr 27, 2016 at 9:49

Docker supports Hyper-V as the driver

You need to perform the following steps:

• Create a virtual switch, refer to this article on how to do that

• Create a docker machine using that network switch and hyper-V driver.

  docker-machine create -d hyperv --hyperv-virtual-switch "name of the virtual switch created above" default
  

I got the same error when I installed Docker Toolbox on my Windows 10 machine.

Solution:

1. Install Docker Community Edition (not Docker Toolbox)
2. Enable Hyper-V

Open Control Panel -> System and Security -> Programs (left panel) -> Turn Windows features on or off -> Check the Hyper-V box

As of 2017’s Win 10, if you don’t have Hyper-V option, then your Windows OS is not Enterprise Edition. Also, Docker seems to work a lot better on Intel processors (not AMD).

1. Add C:Program FilesDockerDockerresourcesbin to Path in Environmental Variables.
2. Open Git Bash and type docker-compose up and now that command should work.

If you don’t have GitBash, please download it.

I was having the same issue, and this blog post solved it. The author runs you through the steps of adding the --virtualbox-no-vtx-check flag to the docker shell script.

Virtualbox and Hyper-V don’t play well together. I am NOT the author.

answered Jun 28, 2016 at 21:58

answered Aug 25, 2017 at 9:09

See if when you run:

docker-machine create -d hyperv --hyperv-virtual-switch "Virtual Switch" default

you get Error with: pre-create check: "Hyper-V PowerShell Module is not available"

If so just enable in Docker(icon on your desktop)->settings->expose daemon on TCP …

answered May 28, 2020 at 15:12

ItharIthar

4,6154 gold badges38 silver badges38 bronze badges