Docker Desktop Will Not Start

[phillmorgan28]

• I have tried with the latest version of Docker Desktop
• I have tried disabling enabled experimental features
• I have uploaded Diagnostics
• Diagnostics ID:

Actual behavior

Docker desktop displays "Docker is starting..." forever

Expected behavior

Docker starts

Information

Version: 4.16.2 (95914)
Sha1: 681dc3e39d6c0f5e6ac7f7b04937fe0738e0cb2a
Started on: 2023/01/20 22:52:34.352
Resources: C:\Program Files\Docker\Docker\resources
OS: Windows 10 Pro
Edition: Professional
Id: 2009
Build: 22623
BuildLabName: 22621.1.amd64fre.ni_release.220506-1250
WSL2

Output of & "C:\Program Files\Docker\Docker\resources\com.docker.diagnose.exe" check

Starting diagnostics

[PASS] DD0027: is there available disk space on the host?
[SKIP] DD0028: is there available VM disk space?
[PASS] DD0002: does the bootloader have virtualization enabled?
[SKIP] DD0018: does the host support virtualization?
[PASS] DD0001: is the application running?
[PASS] DD0022: is the Virtual Machine Platform Windows Feature enabled?
[PASS] DD0021: is the WSL 2 Windows Feature enabled?
[FAIL] DD0024: is WSL installed? exit status 1
[FAIL] DD0025: are WSL distros installed? exit status 1
[PASS] DD0026: is the WSL LxssManager service running?
[FAIL] DD0029: is the WSL 2 Linux filesystem corrupt? context deadline exceeded
[FAIL] DD0035: is the VM time synchronized? exit status 1
[PASS] DD0017: can a VM be started?
[PASS] DD0016: is the LinuxKit VM running?
[FAIL] DD0011: are the LinuxKit services running? failed to ping VM diagnosticsd with error: Get "http://ipc/ping": open \.\pipe\dockerDiagnosticd: The system cannot find the file specified.
[2023-01-20T22:56:21.655784300Z][com.docker.diagnose.exe][I] ipc.NewClient: b4c366a9-diagnose -> \.\pipe\dockerDiagnosticd diagnosticsd
[common/pkg/diagkit/gather/diagnose.glob..func14()
[ common/pkg/diagkit/gather/diagnose/linuxkit.go:18 +0x8b
[common/pkg/diagkit/gather/diagnose.(*test).GetResult(0xddb440)
[ common/pkg/diagkit/gather/diagnose/test.go:46 +0x43
[common/pkg/diagkit/gather/diagnose.Run.func1(0xddb440)
[ common/pkg/diagkit/gather/diagnose/run.go:17 +0x5a
[common/pkg/diagkit/gather/diagnose.walkOnce.func1(0x4?, 0xddb440)
[ common/pkg/diagkit/gather/diagnose/run.go:142 +0x77
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x3, 0xddb440, 0xc000131728)
[ common/pkg/diagkit/gather/diagnose/run.go:151 +0x87
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x2, 0xddb4c0, 0xc000131728)
[ common/pkg/diagkit/gather/diagnose/run.go:148 +0x52
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x1, 0xddb540, 0xc000131728)
[ common/pkg/diagkit/gather/diagnose/run.go:148 +0x52
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x0, 0xddbcc0, 0xc000131728)
[ common/pkg/diagkit/gather/diagnose/run.go:148 +0x52
[common/pkg/diagkit/gather/diagnose.walkOnce(0x76e8a0?, 0xc00035f890)
[ common/pkg/diagkit/gather/diagnose/run.go:137 +0xcc
[common/pkg/diagkit/gather/diagnose.Run(0xddbcc0, 0xdbc20da00000010?, {0xc00035fb20, 0x1, 0x1})
[ common/pkg/diagkit/gather/diagnose/run.go:16 +0x1d4
[main.checkCmd({0xc0000903d0?, 0xc0000903d0?, 0x4?}, {0x0, 0x0})
[ common/cmd/com.docker.diagnose/main.go:138 +0x105
[main.main()
[ common/cmd/com.docker.diagnose/main.go:102 +0x27f
[2023-01-20T22:56:21.655784300Z][com.docker.diagnose.exe][I] (cec72bce) b4c366a9-diagnose C->S diagnosticsd GET /ping
[2023-01-20T22:56:21.656297600Z][com.docker.diagnose.exe][W] (cec72bce) b4c366a9-diagnose C<-S NoResponse GET /ping (513.3µs): Get "http://ipc/ping": open \.\pipe\dockerDiagnosticd: The system cannot find the file specified.

[FAIL] DD0004: is the Docker engine running? Get "http://ipc/docker": open \.\pipe\dockerLifecycleServer: The system cannot find the file specified.
[2023-01-20T22:56:21.657840200Z][com.docker.diagnose.exe][I] ipc.NewClient: 9a2ec43c-com.docker.diagnose -> \.\pipe\dockerLifecycleServer VMDockerdAPI
[linuxkit/pkg/desktop-host-tools/pkg/client.NewClientForPath(...)
[ linuxkit/pkg/desktop-host-tools/pkg/client/client.go:63
[linuxkit/pkg/desktop-host-tools/pkg/client.NewClient({0x833bdc, 0x13})
[ linuxkit/pkg/desktop-host-tools/pkg/client/client.go:57 +0x99
[common/pkg/diagkit/gather/diagnose.isDockerEngineRunning()
[ common/pkg/diagkit/gather/diagnose/dockerd.go:21 +0x29
[common/pkg/diagkit/gather/diagnose.(*test).GetResult(0xddb4c0)
[ common/pkg/diagkit/gather/diagnose/test.go:46 +0x43
[common/pkg/diagkit/gather/diagnose.Run.func1(0xddb4c0)
[ common/pkg/diagkit/gather/diagnose/run.go:17 +0x5a
[common/pkg/diagkit/gather/diagnose.walkOnce.func1(0x3?, 0xddb4c0)
[ common/pkg/diagkit/gather/diagnose/run.go:142 +0x77
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x2, 0xddb4c0, 0xc000131728)
[ common/pkg/diagkit/gather/diagnose/run.go:151 +0x87
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x1, 0xddb540, 0xc000131728)
[ common/pkg/diagkit/gather/diagnose/run.go:148 +0x52
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x0, 0xddbcc0, 0xc000131728)
[ common/pkg/diagkit/gather/diagnose/run.go:148 +0x52
[common/pkg/diagkit/gather/diagnose.walkOnce(0x76e8a0?, 0xc00035f890)
[ common/pkg/diagkit/gather/diagnose/run.go:137 +0xcc
[common/pkg/diagkit/gather/diagnose.Run(0xddbcc0, 0xdbc20da00000010?, {0xc00035fb20, 0x1, 0x1})
[ common/pkg/diagkit/gather/diagnose/run.go:16 +0x1d4
[main.checkCmd({0xc0000903d0?, 0xc0000903d0?, 0x4?}, {0x0, 0x0})
[ common/cmd/com.docker.diagnose/main.go:138 +0x105
[main.main()
[ common/cmd/com.docker.diagnose/main.go:102 +0x27f
[2023-01-20T22:56:21.658352700Z][com.docker.diagnose.exe][I] (116a9d4f) 9a2ec43c-com.docker.diagnose C->S VMDockerdAPI GET /docker
[2023-01-20T22:56:21.658352700Z][com.docker.diagnose.exe][W] (116a9d4f) 9a2ec43c-com.docker.diagnose C<-S NoResponse GET /docker (0s): Get "http://ipc/docker": open \.\pipe\dockerLifecycleServer: The system cannot find the file specified.
[2023-01-20T22:56:21.658352700Z][com.docker.diagnose.exe][I] (116a9d4f-1) 9a2ec43c-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-01-20T22:56:21.658865000Z][com.docker.diagnose.exe][W] (116a9d4f-1) 9a2ec43c-com.docker.diagnose C<-S NoResponse GET /ping (512.3µs): Get "http://ipc/ping": open \.\pipe\dockerLifecycleServer: The system cannot find the file specified.
[2023-01-20T22:56:22.664091900Z][com.docker.diagnose.exe][I] (116a9d4f-2) 9a2ec43c-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-01-20T22:56:22.664091900Z][com.docker.diagnose.exe][W] (116a9d4f-2) 9a2ec43c-com.docker.diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \.\pipe\dockerLifecycleServer: The system cannot find the file specified.
[2023-01-20T22:56:23.674125300Z][com.docker.diagnose.exe][I] (116a9d4f-3) 9a2ec43c-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-01-20T22:56:23.674125300Z][com.docker.diagnose.exe][W] (116a9d4f-3) 9a2ec43c-com.docker.diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \.\pipe\dockerLifecycleServer: The system cannot find the file specified.
[2023-01-20T22:56:24.684439400Z][com.docker.diagnose.exe][I] (116a9d4f-4) 9a2ec43c-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-01-20T22:56:24.685044400Z][com.docker.diagnose.exe][W] (116a9d4f-4) 9a2ec43c-com.docker.diagnose C<-S NoResponse GET /ping (605µs): Get "http://ipc/ping": open \.\pipe\dockerLifecycleServer: The system cannot find the file specified.
[2023-01-20T22:56:25.694116600Z][com.docker.diagnose.exe][I] (116a9d4f-5) 9a2ec43c-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-01-20T22:56:25.694116600Z][com.docker.diagnose.exe][W] (116a9d4f-5) 9a2ec43c-com.docker.diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \.\pipe\dockerLifecycleServer: The system cannot find the file specified.
[2023-01-20T22:56:26.703994100Z][com.docker.diagnose.exe][I] (116a9d4f-6) 9a2ec43c-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-01-20T22:56:26.703994100Z][com.docker.diagnose.exe][W] (116a9d4f-6) 9a2ec43c-com.docker.diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \.\pipe\dockerLifecycleServer: The system cannot find the file specified.
[2023-01-20T22:56:27.714007200Z][com.docker.diagnose.exe][I] (116a9d4f-7) 9a2ec43c-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-01-20T22:56:27.714007200Z][com.docker.diagnose.exe][W] (116a9d4f-7) 9a2ec43c-com.docker.diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \.\pipe\dockerLifecycleServer: The system cannot find the file specified.
[2023-01-20T22:56:28.723915300Z][com.docker.diagnose.exe][I] (116a9d4f-8) 9a2ec43c-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-01-20T22:56:28.724005900Z][com.docker.diagnose.exe][W] (116a9d4f-8) 9a2ec43c-com.docker.diagnose C<-S NoResponse GET /ping (90.6µs): Get "http://ipc/ping": open \.\pipe\dockerLifecycleServer: The system cannot find the file specified.

[PASS] DD0015: are the binary symlinks installed?
[FAIL] DD0031: does the Docker API work? 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_linux/v1.24/containers/json?limit=0": open //./pipe/docker_engine_linux: The system cannot find the file specified.
[PASS] DD0013: is the $PATH ok?
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.
[FAIL] DD0003: is the Docker CLI working? exit status 1
[PASS] DD0005: is the user in the docker-users group?
[PASS] DD0038: is the connection to Docker working?
2023/01/20 22:56:34 exit status 1

Just to say, I've repeatedly uninstalled docker desktop and WSL. All Windows updates have been applied.

I've also attempted manually installing WSL before installing docker desktop and always receive the same errors.

[Broderick890]

the same issue

[synominit]

Same issue here

Edit:
This was a fresh install that I had the issue with.
I've run the following and it fixed it for me;

• Uninstalled the Docker Desktop
• wsl --update
• Restarted computer
• Reinstalled Docker Desktop

[kwam777]

Got the same Issue with Windows.. Just wanted to start with Docker for further education
Any help would be very appreciated!

[NileshGule]

I am facing the same issue. One thing I noted is that the Windows Defender service is running. It could be causing the Docker Desktop to hang.

[hugofintecture]

Same issue for me since Docker Desktop 4.16.2

[foulong]

Same issue.

Concerning @NileshGule remark, i disabled windows defender to test.
No change (docker desktop starts forever).

i'm obliged to reinstall docker desktop v4.15, which runs.

[p1-0tr]

hi, thanks for reporting the issue and sorry for any inconvenience. I've created a dev build with possible fixes, if you are willing to give it a go, here is a link - https://desktop-stage.docker.com/win/main/amd64/96109/Docker%20Desktop%20Installer.exe . Also, in case the problem persists, here - https://docs.docker.com/desktop/troubleshoot/overview/#diagnose-from-the-terminal - you can find instructions on how to create a diagnostic bundle from the CLI, as without logs it's really tricky to determine the root cause.

[jonathansampson]

@p1-0tr That doesn't appear to resolve the issue for me. Please see DC821352-A5DF-4E10-A5B1-FC88B1A7336D/20230123162956 for diagnostics.

[K2ouMais]

hi, thanks for reporting the issue and sorry for any inconvenience. I've created a dev build with possible fixes, if you are willing to give it a go, here is a link - https://desktop-stage.docker.com/win/main/amd64/96109/Docker%20Desktop%20Installer.exe . Also, in case the problem persists, here - https://docs.docker.com/desktop/troubleshoot/overview/#diagnose-from-the-terminal - you can find instructions on how to create a diagnostic bundle from the CLI, as without logs it's really tricky to determine the root cause.

After uninstalling v4.16.2 and unregistering all docker wsl containers and installing the version 4.17.0 seems to work again.

[DarleiC]

Same issue here

Edit: This was a fresh install that I had the issue with. I've run the following and it fixed it for me;

• Uninstalled the Docker Desktop
• wsl --update
• Restarted computer
• Reinstalled Docker Desktop

Thanks😍, just wsl --update and restart it fixed it for me

-- Docker Desktop 4.16.2 (95914) is currently the newest version available.

[hugofintecture]

Had this error while launching the dev build:

Docker.Core.HttpBadResponseException:
{"message":"2 errors occurred:\n\t* terminating WSL distro \"docker-desktop\": terminating WSL distro \"docker-desktop\": exit status 0xffffffff\n\t* unregistering WSL distro \"docker-desktop\": unregistering WSL \"docker-desktop\": winapi error #2147746562\n\n"}

   à Docker.Core.Logging.HttpClientExceptionInterceptor.<InterceptResponseAsync>d__0.MoveNext() dans C:\workspaces\PR-20321\src\github.com\docker\pinata\win\src\Docker.Core\Logging\HttpClientExceptionInterceptor.cs:ligne 26
--- Fin de la trace de la pile à partir de l'emplacement précédent au niveau duquel l'exception a été levée ---
   à System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   à System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   à Docker.Core.IPC.Client.<SendAsync>d__5.MoveNext() dans C:\workspaces\PR-20321\src\github.com\docker\pinata\win\src\Docker.Core\IPC\Client.cs:ligne 42
--- Fin de la trace de la pile à partir de l'emplacement précédent au niveau duquel l'exception a été levée ---
   à System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   à System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   à System.Net.Http.HttpClient.<FinishSendAsyncBuffered>d__58.MoveNext()
--- Fin de la trace de la pile à partir de l'emplacement précédent au niveau duquel l'exception a été levée ---
   à System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   à System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   à Docker.Core.GoBackend.GoBackendClient.<WSLEngineCheckPreconditions>d__42.MoveNext() dans C:\workspaces\PR-20321\src\github.com\docker\pinata\win\src\Docker.Core\GoBackend\GoBackendClient.cs:ligne 405
--- Fin de la trace de la pile à partir de l'emplacement précédent au niveau duquel l'exception a été levée ---
   à System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   à System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   à Docker.Engines.WSL2.LinuxWSL2Engine.<DoCheckPreconditionsAsync>d__19.MoveNext() dans C:\workspaces\PR-20321\src\github.com\docker\pinata\win\src\Docker.Engines\WSL2\LinuxWSL2Engine.cs:ligne 139
--- Fin de la trace de la pile à partir de l'emplacement précédent au niveau duquel l'exception a été levée ---
   à System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   à System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   à Docker.ApiServices.StateMachines.TaskExtensions.<WrapAsyncInCancellationException>d__0.MoveNext() dans C:\workspaces\PR-20321\src\github.com\docker\pinata\win\src\Docker.ApiServices\StateMachines\TaskExtensions.cs:ligne 29
--- Fin de la trace de la pile à partir de l'emplacement précédent au niveau duquel l'exception a été levée ---
   à System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   à System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   à Docker.ApiServices.StateMachines.StartTransition.<DoRunAsync>d__6.MoveNext() dans C:\workspaces\PR-20321\src\github.com\docker\pinata\win\src\Docker.ApiServices\StateMachines\StartTransition.cs:ligne 67
--- Fin de la trace de la pile à partir de l'emplacement précédent au niveau duquel l'exception a été levée ---
   à System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   à System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   à Docker.ApiServices.StateMachines.EngineStateMachine.<StartAsync>d__15.MoveNext() dans C:\workspaces\PR-20321\src\github.com\docker\pinata\win\src\Docker.ApiServices\StateMachines\EngineStateMachine.cs:ligne 72
--- Fin de la trace de la pile à partir de l'emplacement précédent au niveau duquel l'exception a été levée ---
   à System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   à System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   à Docker.Engines.Engines.<StartAsync>d__23.MoveNext() dans C:\workspaces\PR-20321\src\github.com\docker\pinata\win\src\Docker.Engines\Engines.cs:ligne 109

[NileshGule]

I was thinking the issue was due to Windows defender. But I was able to downgrade Docekr Desktop to 4.15.0 version and run it. So the issue is related to the 4.16.1 & 4.16.2 versions.

[p1-0tr]

@jonathansampson and @hugofintecture, thanks for giving the build a go.

I've created another one with further fixes - https://desktop-stage.docker.com/win/main/amd64/96212/Docker%20Desktop%20Installer.exe . I am pretty confident it resolves the issue @jonathansampson is seeing.

@hugofintecture - the issue you are seeing is likely related, but I can't say for sure without full logs. Would you be ok with trying the build above? If the issue persists could would you be ok with collecting diagnostics - https://docs.docker.com/desktop/troubleshoot/overview/#diagnose-from-the-terminal (I am most interested in %LOCALAPPDATA%\Docker\log.txt).

[jonathansampson]

@p1-0tr So far, so good. I installed that build, and the Docker engine is now up and running. I'll return if anything changes.