Docker for windows won't launch

kwsanders · 2021-05-15T06:51:24.926Z

ganeshkonathala:

Switching Daemon helped me to start docker service without any reinstallation.

**C:\Program Files\Docker\Docker> ./DockerCli.exe -SwitchDaemon

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.

sureshnautiyal87 · 2021-05-15T08:38:35.219Z

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.

abydosone · 2021-05-17T22:20:04.171Z

Brilliant Suresh! This has been pestering me for months.This worked great for me.

rruffer · 2021-06-23T19:56:02.022Z

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

aniondev · 2021-07-19T20:21:42.656Z

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.

andiesam · 2021-07-28T13:55:40.205Z

Thanks! It worked for me

zhamdi · 2021-07-30T08:07:32.371Z

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

duncanplayz · 2021-08-15T14:52:04.366Z

This solution worked for me, thanks!

arneeide · 2021-10-06T14:59:14.295Z

It simply doesn’t work… Installation without problems but does not start. So many suggestions here, still no bug fix.

devendran7 · 2021-10-30T07:35:31.338Z

You are Right! I have same issue. I didn’t find proper solution

ark2kar · 2021-12-13T14:13:31.261Z

Confirm that you are member of Hyper-V admins and docker-users Windows local groups. (Not remember exact group names)

anhtu13395 · 2022-02-14T02:14:05.723Z

I have same issue and this solution worked for me.
If your admin account is different to your user account, you must add the user to the docker-users group.

dharsanb · 2022-02-22T13:28:29.319Z

Works like a charm
Thanks

bcheung89 · 2022-03-01T16:23:50.027Z

None of these solutions works for me, I dont even get an error. My container starts 1 sec, and then exits with NO errors… in logs nor eventviewer. Any suggestions to be able to do something?

andeyashwanth · 2022-03-24T09:09:28.480Z

Checked C:\Users\yande\AppData\Local\Docker\log.txt

Version: 4.4.4 (73704)
Sha1: 6619d42de8031291c9306bf94f254f429aab111c
Started on: 2022/03/24 14:30:22.903
Resources: C:\Program Files\Docker\Docker\resources
OS: Windows 10 Enterprise
Edition: Enterprise
Id: 2009
Build: 19043
BuildLabName: 19041.1.amd64fre.vb_release.191206-1406
File: C:\Users\username\AppData\Local\Docker\log.txt
CommandLine: “C:\Program Files\Docker\Docker\Docker Desktop.exe” -SwitchDaemon
You can send feedback, including this log file, at Issues · docker/for-win · GitHub
[14:30:22.979][GUI ][Info ] Starting…
[14:30:23.633][GUI ][Error ] Access denied to Docker. Exiting.

googled the error message and found this post Docker for Windows - Access Denied · Issue #868 · docker/for-win · GitHub.
Added my logged in windows account to the docker users group and logged out and logged into windows. Now docker desktop starts successfully.
I also added -SwitchDaemon to the docker desktop startup shortcut > properties > Target and gave full control to logged in users in security tab of the same docker desktop shortcut’s properties. Not sure if that is also required.

xaxage · 2022-04-03T05:21:05.390Z

Nothing works… Tried everythin!

bennzeppelin · 2022-04-07T23:57:44.004Z

Wasn’t able to start Docker Desktop GUI after deleting all docker related folders in AppData, uninstalling and re-installing the latest version (4.7.0) by running as Admin.
Eventually was able run after installing version 4.4.4 (run installer as admin), available here Docker for Windows release notes | Docker Documentation

ndevathi · 2022-06-14T05:17:50.810Z

This one worked for me. Thanks @xavierkj .

przemek3d · 2023-01-28T18:34:43.132Z

Do not select the recommended option: WSL instead of Hyper-V. Stick with Hyper-V instead.

rimelek · 2023-01-29T23:20:35.080Z

Can you explain why you recommend this? What was your issue that you could solve this way? Using WSL instead of HyperV has multiple benefits so it can’t be a general recommendation. Just to mention one: HyperV is not available in Windows Home, but WSL is.