I’ve been running & using Docker Desktop 4.18 daily for some time. After restarting my machine on 4/12, I started seeing the following error when Docker Desktop tries to start:
Docker.Core.HttpBadResponseException:
no response content
at Docker.Core.GoBackend.GoBackendClient.<PostNoBodyWithError>d__21.MoveNext() in C:\workspaces\PR-21378\src\github.com\docker\pinata\win\src\Docker.Core\GoBackend\GoBackendClient.cs:line 228
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Docker.Engines.WindowsContainersEngine.<DoStartAsync>d__10.MoveNext() in C:\workspaces\PR-21378\src\github.com\docker\pinata\win\src\Docker.Engines\WindowsContainersEngine.cs:line 50
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Docker.ApiServices.StateMachines.TaskExtensions.<WrapAsyncInCancellationException>d__0.MoveNext() in C:\workspaces\PR-21378\src\github.com\docker\pinata\win\src\Docker.ApiServices\StateMachines\TaskExtensions.cs:line 29
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Docker.ApiServices.StateMachines.StartTransition.<DoRunAsync>d__7.MoveNext() in C:\workspaces\PR-21378\src\github.com\docker\pinata\win\src\Docker.ApiServices\StateMachines\StartTransition.cs:line 79
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at Docker.ApiServices.StateMachines.StartTransition.<DoRunAsync>d__7.MoveNext() in C:\workspaces\PR-21378\src\github.com\docker\pinata\win\src\Docker.ApiServices\StateMachines\StartTransition.cs:line 108
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Docker.ApiServices.StateMachines.EngineStateMachine.<StartAsync>d__17.MoveNext() in C:\workspaces\PR-21378\src\github.com\docker\pinata\win\src\Docker.ApiServices\StateMachines\EngineStateMachine.cs:line 97
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Docker.Engines.Engines.<StartAsync>d__24.MoveNext() in C:\workspaces\PR-21378\src\github.com\docker\pinata\win\src\Docker.Engines\Engines.cs:line 124
I’ve tried:
- Uninstalling and reinstalling both WSL and Docker Desktop
- Upgrading WSL to latest pre-release 1.2.2
But haven’t had any luck. I’ve found that Linux containers work but switching to Windows containers always results in the above.
There seem to be recent reports of similar issues from the GitHub repo issues: Docker 4.18 Fails to Start After Latest WSL Update · Issue #13391 · docker/for-win · GitHub
It tried a suggestion to upgrade WSL to pre-release there but as mentioned this didn’t work.
Versions:
WSL 1.2.0.0 & (tried 1.2.2.0)
Docker Desktop 4.18
Windows Version 10.0.22621 Build 22621
Has anyone run into this and are there any suggestions to unblock? Thanks!