For me “Docker Service for Windows” was not running for some reason. Opened “Services” and started it from there, now Docker works.
I also had the same problem with docker desktop 2.5.01. After restart the docker was not starting properly and manual start of the service also failed. But the following steps have worked.
- From search start “System Configuration” application.
- From the application go to the Services tab and select the ‘Power’ service.
- Untick the Power service and restart the machine.
- The Docker desktop service will be automatically started.
2 Likes
I found a file ‘.trackid’ in folder C:\Users{Username}\AppData\Roaming\Docker, I removed it then the installer dialog was presented
hey did anyone figured out how to launch docker dekstop
hey , did you figured out how to launch docker dekstop?
I have Docker desktop(3.3.0) service running in the Services in Windows 10 Enterprise version 1909 , but restarting the service is still not running the docker for windows. Even when I load the settings screen , it goes on loading… so not able to click ‘Apply and Restart’ button
1 Like
The same goes for me. After latest update of docker it stopped working
I’ve removed it, installed older version. It worked after that.
But after I rebooted my PC docker applied update automatically again. and once again stopped working.
It is hanning right now now on settings screen, and there are no options in context menu to stop/restart docker
I had the same issue after an upgrade today and this worked for me: Open an elevated PowerShell prompt and enter:
& 'C:\Program Files\Docker\Docker\DockerCli.exe' -SwitchDaemon
5 Likes
I have same issue and need to run the DockerCli.exe command every time I restart my computer, and I have menu options missing.
You can Reset to factory defaults docker container
I have too, but the thing keeps telling me Hyper-V is no enabled
I am trying to determine if a recent Windows Update has broken docker functionality in the AWS " Windows_Server-20H2-English-Core-ECS_Optimized" AMI.
All other Windows-based “ECS_Optimized” AMIs can run ‘docker run hello-world’, however this AMI produces an error saying:
The container operating system does not match the host operating system.
C:\Users\Administrator>docker run hello-world
docker: Error response from daemon: hcsshim::CreateComputeSystem b4bcb6998099366427f193a966ebf07b4a18ef428e966b9f0450f6109ce2c60c: The container operating system does not match the host operating system.
(extra info: {“SystemType”:“Container”,“Name”:“b4bcb6998099366427f193a966ebf07b4a18ef428e966b9f0450f6109ce2c60c”,“Owner”:“docker”,“VolumePath”:“\\?\Volume{d19b3595-df8a-4694-a1bd-c9072d8f62c6}”,“IgnoreFlushesDuringBoot”:true,“LayerFolderPath”:“C:\ProgramData\docker\windowsfilter\b4bcb6998099366427f193a966ebf07b4a18ef428e966b9f0450f6109ce2c60c”,“Layers”:[{“ID”:“f6b4264e-8ec7-5de6-8015-83806cbd6b31”,“Path”:“C:\ProgramData\docker\windowsfilter\4a07f939f9782ca7e737d436551b6d0a1341258d4963c6a42ea26f6e786ca57d”},{“ID”:“bc27a84c-db85-5e23-8094-330a8ccadedc”,“Path”:“C:\ProgramData\docker\windowsfilter\4ab7edb603f9ca6a57a3b532a6aeee7274f7d379b46f05e2e4111ee0c0dbbe73”},{“ID”:“2a987fec-a973-5771-bc43-6dc9ef9f0ecc”,“Path”:“C:\ProgramData\docker\windowsfilter\f68871e12777d530cb26eaff4356c40d54d1a5a82623c4267dbb652aa29f34fa”}],“HostName”:“b4bcb6998099”,“HvPartition”:false,“EndpointList”:[“9b748944-2a9b-4154-b2fb-ef5ce16edf70”],“AllowUnqualifiedDNSQuery”:true}).
Considering ECS relies on docker functionality this AMI is broken to my perspective.
Switching Daemon helped me to start docker service without any reinstallation.
**C:\Program Files\Docker\Docker> ./DockerCli.exe -SwitchDaemon
Hope this helps
1 Like
I was having this problem after switching to Windows container and later back to Linux containers this evening. I used this command specified and I was able to load Docker Desktop again.
I faced same issue. Docker engine is not starting while launching docker desktop. What I have tried is logout and login back in docker account via docker desktop. It has restarted docker engine and docker start working fine. If this helps with your problem it will be great.
2 Likes
Brilliant Suresh! This has been pestering me for months.This worked great for me. 
I tried the methods above but it didn’t work. What worked for me was deleting the Docker and Docker Desktop folders in AppData\Roaming
1 Like
I had this problem when I changed the daemon.json-file (located in C:\users<username>.docker). I figured out that of course the file must contain valid json and in my case that was the reason for not starting without any error-message.
Thanks! It worked for me
I had this error, and none of the above solutions worked for me (deleted working files, reinstalled, run the command -switchDeamon):
It showed out that the origin of the error could be Kaspersky that is locking some features having linx in windows, since I realized that even my Ubuntu under windows didn’t start. For that I found a fix here that made docker work back too: WslRegisterDistribution failed with 0x80070422 · Issue #3815 · microsoft/WSL · GitHub where you should basically run in a CMD windows with administrator rights:
sc config LxssManager start=auto
Just for a reference and for others to be able to find the error in google, here’s the error I was getting:
System.InvalidOperationException:
Failed to deploy distro docker-desktop to C:\Users\Zied\AppData\Local\Docker\wsl\distro: exit code: -1
stdout: Le service ne peut pas être démarré parce qu’il est désactivé ou qu’aucun périphérique activé ne lui est associé.
stderr:
à Docker.ApiServices.WSL2.WslShortLivedCommandResult.LogAndThrowIfUnexpectedExitCode(String prefix, ILogger log, Int32 expectedExitCode) dans \workspaces\PR-16070\src\github.com\docker\pinata\win\src\Docker.ApiServices\WSL2\WslCommand.cs:ligne 146
à Docker.Engines.WSL2.WSL2Provisioning.d__17.MoveNext() dans
2 Likes