search

docker / for-win

Bug reports for Docker Desktop for Windows
https://www.docker.com/products/docker#/windows
1.86k stars 289 forks source link

Docker Desktop Will Not Start #13184

Closed phillmorgan28 closed 1 year ago

phillmorgan28 commented 1 year ago

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 commented 1 year ago

the same issue

synominit commented 1 year ago

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;

kwam777 commented 1 year ago

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

NileshGule commented 1 year ago

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. docker-desktop-defender-error

hugofintecture commented 1 year ago

Same issue for me since Docker Desktop 4.16.2

foulong commented 1 year ago

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 commented 1 year ago

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 commented 1 year ago

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

K2ouMais commented 1 year ago

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 commented 1 year ago

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 commented 1 year ago

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 commented 1 year ago

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 commented 1 year ago

@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 commented 1 year ago

@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.

hugofintecture commented 1 year ago

@p1-0tr Good for me also now, thanks!

diablodale commented 1 year ago

@p1-0tr, I'm not in a place to try a private build of DD. Though, I'm happy to provide the docker appdatalocal docker logs you requested in a dup bug...

When 4.16.2 failed to start after upgrade....I tried 4.16.1 and then 4.15. All fail to start...yet those earlier versions worked for me...I upgraded from them. This suggests to me there is a change that is external change to DD that is now affecting it. Two days ago Windows Update installed KB4023057, and Windows Defender is automatically pushing updates.

dd-4.15.0.txt dd-4.16.1.txt

Noticed 4.16.1 migrated features.json. When 4.16.1 failed, I uninstalled. Then installed 4.15 and on its failed start I can see in the log invalid feature config at <HOME>\.docker\features.json.

p1-0tr commented 1 year ago

@diablodale thanks for providing the logs. This looks quite odd, the following logs look worrying to me:

[2023-01-25T04:36:56.316863800Z][WSL2Provisioning][E] Failed to terminate distro: exit code: -1
 stdout: There is no distribution with the supplied name.
Error code: Wsl/Service/WSL_E_DISTRO_NOT_FOUND

That condition should not happen, because we make sure our distros exist before trying to terminate (or do anything else with them).

Off the top of my head I can suggest trying to wsl --shutdown and then try starting DD again. (Also I wonder if this could be related to https://github.com/microsoft/WSL/issues/9331).

Also could you run wsl -l -v --all and if docker-desktop-data and/or docker-desktop are listed try running:

wsl -d docker-desktop -e /bin/uname
wsl -d docker-desktop-data -e /wsl-keepalive

and see if those produce any errors?

todorinskiz commented 1 year ago

Simply wsl --update fixed it for me, no restarts needed

mat007 commented 1 year ago

Hey everyone, we’re thinking we have made significant progress to fix several separate root causes for this «starting forever» issue. We’re going to release a Docker Desktop 4.16.3 with these fixes. Here is the release candidate, if you wanted to try it out. Thanks!

hugofintecture commented 1 year ago

Hi! Works for me. Thank you very much.

Jerome2103 commented 1 year ago

We’re going to release a Docker Desktop 4.16.3 with these fixes.

Thank you, now working again ;)

diablodale commented 1 year ago

Off the top of my head I can suggest trying to wsl --shutdown and then try starting DD again. (Also I wonder if this could be related to microsoft/WSL#9331).

In between un/re/installs the machine was often rebooted; naturally that shuts everything down. WSL2 has been working well before, during, and after this DD issue. However, when DD hangs on startup, also launching a new wsl distro session hangs.

Before/during/after the problematic DD upgrade, WSL2 works without flaw. I"m currently using docker-ce within my WSL2 Ubuntu distro with no issues. Nothing above about --updates or other WSL2 changes have been done/needed. I have no symptoms that match wsl issue 9331.

Also could you run wsl -l -v --all and if docker-desktop-data and/or docker-desktop are listed try running:

wsl -d docker-desktop -e /bin/uname
wsl -d docker-desktop-data -e /wsl-keepalive

and see if those produce any errors?

  1. I edited my wsl .profile to NOT launch docker-ce manually
  2. wsl --shutdown
  3. run DD 4.15.0 app. It was still installed from attempts earlier this week.
  4. wait for fail...

Fails. DD app red whale and "Docker desktop failed to start." Running...

C:\Users\dale>wsl -l -v --all
  NAME              STATE           VERSION
* Ubuntu-20.04      Running         2
  Ubuntu-18.04      Stopped         2
  docker-desktop    Uninstalling    2

therefore I can't do the second set of diagnostics you requested.

mat007 commented 1 year ago

@diablodale do you run the diagnostics tool from the command line?

diablodale commented 1 year ago

[EDITED: replaced previous diag-1 output -- it was taken with docker-ce running within WSL2]

DD fails to start. docker-ce is not running within WSL2 Attached is com.docker.diagnose.exe check Mainly errors that docker is not running and cascade errors from that. Notice on line 136 the diagnostic check itself was hung and I had to press ctrl-c. dock-diag-2.txt

diablodale commented 1 year ago

The key symptom in my scenario is the errant wsl distro state docker-desktop Uninstalling 2 as seen in my post above. This Uninstalling state persisted throughout multiple DD installs, uninstalls, and reboots across versions 4.15-4.16.x versions. None of the docker installers detected and corrected this errant state.

To correct the scenario...

  1. I manually unregistered the system distro...

    C:\Users\dale>wsl -l -v --all
 NAME              STATE           VERSION
* Ubuntu-20.04      Stopped         2
 Ubuntu-18.04      Stopped         2
 docker-desktop    Uninstalling    2

C:\Users\dale>wsl --unregister docker-desktop
Unregistering.
The operation completed successfully.

C:\Users\dale>wsl -l -v --all
 NAME            STATE           VERSION
* Ubuntu-20.04    Stopped         2
 Ubuntu-18.04    Stopped         2

C:\Users\dale>
  2. Installed DD 4.15
  3. Then successfully started DD. The docker service is running and working as expected.

Educated Guesses

I suspect that during uninstall of DD (perhaps the problematic DD 4.16.2), that the uninstall/unregister of the docker-desktop system distro hung or was incomplete. Then later installs/uninstalls of DD didn't detect/correct the issue. Only when the DD app itself ran does it fail (and not correct).

My suggestion is on DD uninstall it should check that distros are successfully uninstalled/unregistered. And DD installs should detect if the two system distros are present and/or in a bad state. And both should attempt to correct or abort/rollback.

mat007 commented 1 year ago

We have just released a Docker Desktop 4.16.3 based on the previously posted RC here in this issue. It should also correctly uninstall/unregister Docker Desktop distros upon uninstall. See https://docs.docker.com/desktop/release-notes/#4163

I’ll close this ticket now, but if you’re still seeing this error, feel free to comment again and upload diagnostics, and we’ll investigate further.

Thanks!

ozzyknox commented 1 year ago

Hi. I am running Windows 11 and am getting the neverending "Docker Desktop starting..." message. I just installed DD v4.16.3.

Windows details: Edition Windows 11 Home Version 22H2 Installed on ‎02/‎10/‎2022 OS build 22621.1105 Experience Windows Feature Experience Pack 1000.22638.1000.0

I ran the diagnostics and got this ID: 8C8A77E6-64DD-4107-9305-6D0D7CC400BE/20230202185116

rhxadbc commented 1 year ago

i've managed to start 4.16.3 version successfully by applying "wsl --shutdown" command in terminal and then restart docker desktop in windows 10.

Zaffer commented 1 year ago

Version 4.16.3 causes error on startup now:

Docker.Core.HttpBadResponseException:
{"message":"1 error occurred:\n\t* starting WSL integration service: synchronising agents: starting added distros: 1 error occurred:\n\t* waiting for WSL integration for Ubuntu-22.04: timed out while polling for WSL distro integration to become ready in \"Ubuntu-22.04\"\n\n\n\n"}

I uninstalled, deleted AppData folder Docker and Docker Desktop. Restarted. Reinstalled. Same problem.

kethahel99 commented 1 year ago

I have the same problem with Version 4.16.3


{"message":"1 error occurred:\n\t* starting WSL integration service: synchronising agents: starting added distros: 1 error occurred:\n\t* waiting for WSL integration for Ubuntu-22.04: timed out while polling for WSL distro integration to become ready in \"Ubuntu-22.04\"\n\n\n\n"}```
p1-0tr commented 1 year ago

hi @Zaffer and @kethahel99 , does the issue persist after running wsl --shutdown on the CLI? If so could you edit %userprofile%\AppData\Roaming\Docker\settings.json such that

  "integratedWslDistros": [],
  "enableIntegrationWithDefaultWslDistro": false,

and see if DD starts with those settings changed?

Emil-Valentin-Toma commented 1 year ago

My Docker install on W10 home edition was plagued with "The network name cannot be found", "unable to calculate the image size" - - kind of errors. Also testing "hello-world" docker image didn't work either. Apart for the obvious culprits, like WSL2, hypervisor, Hyper-V and their related errors, I found particularly that DNS cache (aka DNS-client service) related errors were not addressed in the forums and blogs that I visited initially. A suspicion about the network issues deepened when WSL2 failed to install the Ubuntu image. The reason was the RPC service. However, RPC service was running. It was the DNS-client that was completely disabled and greyed-out. I succeeded to restart it experimenting with the suggestions found at https://www.thewindowsclub.com/enable-the-dns-client-service-if-greyed-out Personally I preferred service auto-restart, so I replaced the value in the "Start" registry entry with "2". After registry editing I found that is not enough to refresh the services. In my case I needed a full restart to settle the DNS service to auto-start AND running.

Ultimately, Hyper-V install may help as an alternative to the WSL2 Linux containers. Be aware, is documented that Oracle VM VirtualBox installations may interfere with Hyper-V. Below is the script that helped me install Hyper-V on w10 home edition. I followed these instruction and was able to install and activate Hyper-V. https://pastebin.com/cX6nupy4

Best of luck!

wixregiga commented 1 year ago

None of these worked. To have such a large problem and just not handle it is unacceptable. I'm downgrading and if that doesn't work, I'm just going to say goodbye to docker

BourneNeo commented 1 year ago

same issue here, why this closed? solved? what's the solution?

ntx-ben commented 1 year ago

Having the same issue.

Uninstalled previous 4.15 version, remove all directories and files related to docker, restarted Windows, installed 4.17.1 and faced with the Docker Starting message.

Running Windows 11 21H2 build 22000.1696 with WSL 2.

I see the in docker.log and lifecycle-server.log the following over and over again:

[2023-03-27T16:15:06.688108714Z][docker][I] [2023-03-27T16:15:06.687339890Z][lifecycle-server][I] proxy >> HEAD /_ping
[2023-03-27T16:15:06.688112185Z][docker][I] [2023-03-27T16:15:06.687631644Z][lifecycle-server][W] dial unix /run/guest-services/docker.sock: connect: no such file or directory
[2023-03-27T16:15:06.789830612Z][docker][I] [2023-03-27T16:15:06.789063869Z][lifecycle-server][I] proxy >> HEAD /_ping
[2023-03-27T16:15:06.789929260Z][docker][I] [2023-03-27T16:15:06.789341879Z][lifecycle-server][W] dial unix /run/guest-services/docker.sock: connect: no such file or directory
[2023-03-27T16:15:06.855112607Z][docker][I] [2023-03-27T16:15:06.854467423Z][lifecycle-server][W] internal networking still not working after 4m52.880181245s: lookup gateway.docker.internal on 192.168.65.7:53: read udp 192.168.65.4:56505->192.168.65.7:53: i/o timeout
[2023-03-27T16:15:06.891389662Z][docker][I] [2023-03-27T16:15:06.890766033Z][lifecycle-server][I] proxy >> HEAD /_ping
[2023-03-27T16:15:06.891845683Z][docker][I] [2023-03-27T16:15:06.891236355Z][lifecycle-server][W] dial unix /run/guest-services/docker.sock: connect: no such file or directory
[2023-03-27T16:15:06.993514276Z][docker][I] [2023-03-27T16:15:06.992705956Z][lifecycle-server][I] proxy >> HEAD /_ping
[2023-03-27T16:15:06.993967454Z][docker][I] [2023-03-27T16:15:06.993340017Z][lifecycle-server][W] dial unix /run/guest-services/docker.sock: connect: no such file or directory

Other details:

docker context ls
NAME                TYPE                DESCRIPTION                               DOCKER ENDPOINT                             KUBERNETES ENDPOINT                  ORCHESTRATOR
default *           moby                Current DOCKER_HOST based configuration   npipe:////./pipe/docker_engine              https://10.0.14.180:6443 (default)   swarm
desktop-linux       moby                                                          npipe:////./pipe/dockerDesktopLinuxEngine
wsl --list --all --verbose
  NAME                   STATE           VERSION
* Ubuntu                 Running         2
  docker-desktop         Running         2
  docker-desktop-data    Running         2
"C:\Program Files\Docker\Docker\resources\com.docker.diagnose.exe" check
[2023-03-27T16:24:26.137815600Z][com.docker.diagnose.exe][I] set path configuration to OnHost
Starting diagnostics

[PASS] DD0027: is there available disk space on the host?
[PASS] 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?
[PASS] DD0024: is WSL installed?
[PASS] DD0025: are WSL distros installed?
[PASS] DD0026: is the WSL LxssManager service running?
[PASS] DD0029: is the WSL 2 Linux filesystem corrupt?
[PASS] DD0035: is the VM time synchronized?
[PASS] DD0017: can a VM be started?
[PASS] DD0016: is the LinuxKit VM running?
[PASS] DD0011: are the LinuxKit services running?
[FAIL] DD0004: is the Docker engine running? docker engine is still starting, waiting for internal network to respond for 4m18.314802925s
[2023-03-27T16:24:29.664993300Z][com.docker.diagnose.exe][I] ipc.NewClient: 4d5e843a-com.docker.diagnose -> \\.\pipe\dockerLifecycleServer VMDockerdAPI
[2023-03-27T16:24:29.665519700Z][com.docker.diagnose.exe][I] (efd6f756) 4d5e843a-com.docker.diagnose C->S VMDockerdAPI GET /docker
[2023-03-27T16:24:29.671437900Z][com.docker.diagnose.exe][I] (efd6f756) 4d5e843a-com.docker.diagnose C<-S fcf490a9-VMDockerdAPI GET /docker (5.9182ms): {"current_action":"waiting for internal network to respond","current_action_start":"2023-03-27T16:20:11.357195675Z","engine":"starting","error":""}

[PASS] DD0015: are the binary symlinks installed?
[FAIL] DD0031: does the Docker API work? Error response from daemon: dial unix /run/guest-services/docker.sock: connect: no such file or directory
[PASS] DD0013: is the $PATH ok?
Error response from daemon: dial unix /run/guest-services/docker.sock: connect: no such file or directory
[FAIL] DD0003: is the Docker CLI working? exit status 1
[FAIL] DD0005: is the user in the docker-users group? The specified domain either does not exist or could not be contacted.
[PASS] DD0038: is the connection to Docker working?
[PASS] DD0014: are the backend processes running?
[PASS] DD0007: is the backend responding?
[PASS] DD0008: is the native API responding?
[PASS] DD0009: is the vpnkit API responding?
[PASS] DD0010: is the Docker API proxy responding?
[PASS] DD0006: is the Docker Desktop Service responding?
[SKIP] DD0030: is the image access management authorized?
[PASS] DD0033: does the host have Internet access?
[PASS] DD0002: does the bootloader have virtualization enabled?
[PASS] 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?
[PASS] DD0024: is WSL installed?
[PASS] DD0025: are WSL distros installed?
[PASS] DD0026: is the WSL LxssManager service running?
[PASS] DD0029: is the WSL 2 Linux filesystem corrupt?
[PASS] DD0035: is the VM time synchronized?
[PASS] DD0017: can a VM be started?
[PASS] DD0016: is the LinuxKit VM running?
[PASS] DD0011: are the LinuxKit services running?
[WARN] DD0004: is the Docker engine running? docker engine is still starting, waiting for internal network to respond for 4m18.314802925s
[PASS] DD0015: are the binary symlinks installed?
[WARN] DD0031: does the Docker API work? Error response from daemon: dial unix /run/guest-services/docker.sock: connect: no such file or directory
[WARN] DD0032: do Docker networks overlap with host IPs? Error response from daemon: dial unix /run/guest-services/docker.sock: connect: no such file or directory

Please note the following 3 warnings:

1 : The check: is the Docker engine running?
    Produced the following warning: docker engine is still starting, waiting for internal network to respond for 4m18.314802925s

The Docker engine manages all containers and images on the host. Check the dockerd.log to see why it failed to start.

2 : The check: does the Docker API work?
    Produced the following warning: Error response from daemon: dial unix /run/guest-services/docker.sock: connect: no such file or directory

If the Docker API is not available from the host then Docker Desktop will not work correctly.

3 : The check: do Docker networks overlap with host IPs?
    Produced the following warning: Error response from daemon: dial unix /run/guest-services/docker.sock: connect: no such file or directory

If the subnet used by a Docker network overlaps with an IP used by the host, then containers
won't be able to contact the overlapping IP addresses.

Try configuring the IP address range used by networks: in your docker-compose.yml.
See https://docs.docker.com/compose/compose-file/compose-file-v2/#ipv4_address-ipv6_address

Please investigate the following 2 issues:

1 : The test: is the Docker engine running?
    Failed with: docker engine is still starting, waiting for internal network to respond for 4m18.314802925s

The Docker engine manages all containers and images on the host. Check the dockerd.log to see why it failed to start.

2 : The test: is the user in the docker-users group?
    Failed with: The specified domain either does not exist or could not be contacted.

The current user must be member of the docker-users group. Press the Win + R keys to open Run, type lusrmgr.msc into Run, followed by Enter to open Local Users and Groups.
EoinLynch2 commented 1 year ago

@p1-0tr Hi, I'm hoping you can help me.. I have the dreaded "Docker is starting" forever warning and I've spent the last 2 days trying to resolve it. Previously docker desktop was running fine for me but since Monday it refuses to start. Posting it in this thread as this one seems to describe most accurately what I'm dealing with...

I feel I have tried everything and I'm losing patience. A brief summary of what I've tried

Restarting laptop countless times Enabling and disabling WSL and Hyper V Attempted to switch to windows containers Fresh install of latest docker desktop Install of various older docker desktop versions (4.18, 4.13, 4.16, 4.17) Deleted user ".docker" folder Deleted appdata docker folders Various wsl commands such as shutdown Force starting LxssManager

Noteworthy:

When the docker desktop is infinitely starting, any wsl commands seem to hang infinitely also. As far as I can tell, the docker-desktop and docker-desktop-data distros are installed correctly. Running "wsl --status" outputs: Default Distribution: docker-desktop-data Default Version: 2 The version of docker desktop currently installed is 4.18.0

Including the logs of "docker.diagnose.exe check"

** I am most concerned by the lines: ***

[FAIL] DD0024: is WSL installed? exit status 1 [FAIL] DD0025: are WSL distros installed? exit status 1

Full output: Starting diagnostics

[PASS] DD0027: is there available disk space on the host? [PASS] 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-04-19T08:51:40.007064900Z][com.docker.diagnose.exe][I] ipc.NewClient: b412c186-diagnose -> \.\pipe\dockerDiagnosticd diagnosticsd [2023-04-19T08:51:40.007614800Z][com.docker.diagnose.exe][I] (d7b604fd) b412c186-diagnose C->S diagnosticsd GET /ping [2023-04-19T08:51:40.008173600Z][com.docker.diagnose.exe][W] (d7b604fd) b412c186-diagnose C<-S NoResponse GET /ping (558.8µ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-04-19T08:51:40.009726900Z][com.docker.diagnose.exe][I] ipc.NewClient: 4e349cd6-com.docker.diagnose -> \.\pipe\dockerLifecycleServer VMDockerdAPI [2023-04-19T08:51:40.009726900Z][com.docker.diagnose.exe][I] (3d393c91) 4e349cd6-com.docker.diagnose C->S VMDockerdAPI GET /docker [2023-04-19T08:51:40.010237300Z][com.docker.diagnose.exe][W] (3d393c91) 4e349cd6-com.docker.diagnose C<-S NoResponse GET /docker (510.4µs): Get "http://ipc/docker": open \.\pipe\dockerLifecycleServer: The system cannot find the file specified. [2023-04-19T08:51:40.010280900Z][com.docker.diagnose.exe][I] (3d393c91-1) 4e349cd6-com.docker.diagnose C->S VMDockerdAPI GET /ping [2023-04-19T08:51:40.010280900Z][com.docker.diagnose.exe][W] (3d393c91-1) 4e349cd6-com.docker.diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \.\pipe\dockerLifecycleServer: The system cannot find the file specified. [2023-04-19T08:51:41.019339400Z][com.docker.diagnose.exe][I] (3d393c91-2) 4e349cd6-com.docker.diagnose C->S VMDockerdAPI GET /ping [2023-04-19T08:51:41.021109100Z][com.docker.diagnose.exe][W] (3d393c91-2) 4e349cd6-com.docker.diagnose C<-S NoResponse GET /ping (1.7697ms): Get "http://ipc/ping": open \.\pipe\dockerLifecycleServer: The system cannot find the file specified. [2023-04-19T08:51:42.026506800Z][com.docker.diagnose.exe][I] (3d393c91-3) 4e349cd6-com.docker.diagnose C->S VMDockerdAPI GET /ping [2023-04-19T08:51:42.027644800Z][com.docker.diagnose.exe][W] (3d393c91-3) 4e349cd6-com.docker.diagnose C<-S NoResponse GET /ping (1.138ms): Get "http://ipc/ping": open \.\pipe\dockerLifecycleServer: The system cannot find the file specified. [2023-04-19T08:51:43.033872400Z][com.docker.diagnose.exe][I] (3d393c91-4) 4e349cd6-com.docker.diagnose C->S VMDockerdAPI GET /ping [2023-04-19T08:51:43.036081600Z][com.docker.diagnose.exe][W] (3d393c91-4) 4e349cd6-com.docker.diagnose C<-S NoResponse GET /ping (1.6096ms): Get "http://ipc/ping": open \.\pipe\dockerLifecycleServer: The system cannot find the file specified. [2023-04-19T08:51:44.042196900Z][com.docker.diagnose.exe][I] (3d393c91-5) 4e349cd6-com.docker.diagnose C->S VMDockerdAPI GET /ping [2023-04-19T08:51:44.042196900Z][com.docker.diagnose.exe][W] (3d393c91-5) 4e349cd6-com.docker.diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \.\pipe\dockerLifecycleServer: The system cannot find the file specified. [2023-04-19T08:51:45.054784200Z][com.docker.diagnose.exe][I] (3d393c91-6) 4e349cd6-com.docker.diagnose C->S VMDockerdAPI GET /ping [2023-04-19T08:51:45.056607600Z][com.docker.diagnose.exe][W] (3d393c91-6) 4e349cd6-com.docker.diagnose C<-S NoResponse GET /ping (1.7878ms): Get "http://ipc/ping": open \.\pipe\dockerLifecycleServer: The system cannot find the file specified. [2023-04-19T08:51:46.057641500Z][com.docker.diagnose.exe][I] (3d393c91-7) 4e349cd6-com.docker.diagnose C->S VMDockerdAPI GET /ping [2023-04-19T08:51:46.059372400Z][com.docker.diagnose.exe][W] (3d393c91-7) 4e349cd6-com.docker.diagnose C<-S NoResponse GET /ping (1.7309ms): Get "http://ipc/ping": open \.\pipe\dockerLifecycleServer: The system cannot find the file specified. [2023-04-19T08:51:47.062035500Z][com.docker.diagnose.exe][I] (3d393c91-8) 4e349cd6-com.docker.diagnose C->S VMDockerdAPI GET /ping [2023-04-19T08:51:47.064300800Z][com.docker.diagnose.exe][W] (3d393c91-8) 4e349cd6-com.docker.diagnose C<-S NoResponse GET /ping (2.2653ms): 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 [FAIL] DD0005: is the user in the docker-users group? The user name could not be found. [PASS] DD0038: is the connection to Docker working? [FAIL] DD0014: are the backend processes running? 2 errors occurred:

[PASS] DD0007: is the backend responding? [PASS] DD0008: is the native API responding? [FAIL] DD0009: is the vpnkit API responding? open \.\pipe\dockerVpnKitDiagnostics: The system cannot find the file specified. [FAIL] DD0010: is the Docker API proxy responding? failed to ping Docker proxy API with error: Get "http://ipc/desktop-diagnostics/ping": open \.\pipe\dockerDesktopLinuxEngine: The system cannot find the file specified. [2023-04-19T08:52:18.165694100Z][com.docker.diagnose.exe][I] ipc.NewClient: 2dc18ba4-diagnose -> \.\pipe\dockerDesktopLinuxEngine Proxy [2023-04-19T08:52:18.165694100Z][com.docker.diagnose.exe][I] (202e64de) 2dc18ba4-diagnose C->S Proxy GET /desktop-diagnostics/ping [2023-04-19T08:52:18.166214400Z][com.docker.diagnose.exe][W] (202e64de) 2dc18ba4-diagnose C<-S NoResponse GET /desktop-diagnostics/ping (520.3µs): Get "http://ipc/desktop-diagnostics/ping": open \.\pipe\dockerDesktopLinuxEngine: The system cannot find the file specified. [2023-04-19T08:52:18.166214400Z][com.docker.diagnose.exe][I] (202e64de-1) 2dc18ba4-diagnose C->S Proxy GET /ping [2023-04-19T08:52:18.166214400Z][com.docker.diagnose.exe][W] (202e64de-1) 2dc18ba4-diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \.\pipe\dockerDesktopLinuxEngine: The system cannot find the file specified. [2023-04-19T08:52:19.175576300Z][com.docker.diagnose.exe][I] (202e64de-2) 2dc18ba4-diagnose C->S Proxy GET /ping [2023-04-19T08:52:19.176086400Z][com.docker.diagnose.exe][W] (202e64de-2) 2dc18ba4-diagnose C<-S NoResponse GET /ping (861.8µs): Get "http://ipc/ping": open \.\pipe\dockerDesktopLinuxEngine: The system cannot find the file specified. [2023-04-19T08:52:20.190516000Z][com.docker.diagnose.exe][I] (202e64de-3) 2dc18ba4-diagnose C->S Proxy GET /ping [2023-04-19T08:52:20.191164700Z][com.docker.diagnose.exe][W] (202e64de-3) 2dc18ba4-diagnose C<-S NoResponse GET /ping (127.8µs): Get "http://ipc/ping": open \.\pipe\dockerDesktopLinuxEngine: The system cannot find the file specified. [2023-04-19T08:52:21.191730200Z][com.docker.diagnose.exe][I] (202e64de-4) 2dc18ba4-diagnose C->S Proxy GET /ping [2023-04-19T08:52:21.192276800Z][com.docker.diagnose.exe][W] (202e64de-4) 2dc18ba4-diagnose C<-S NoResponse GET /ping (546.6µs): Get "http://ipc/ping": open \.\pipe\dockerDesktopLinuxEngine: The system cannot find the file specified. [2023-04-19T08:52:22.205275200Z][com.docker.diagnose.exe][I] (202e64de-5) 2dc18ba4-diagnose C->S Proxy GET /ping [2023-04-19T08:52:22.205275200Z][com.docker.diagnose.exe][W] (202e64de-5) 2dc18ba4-diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \.\pipe\dockerDesktopLinuxEngine: The system cannot find the file specified. [2023-04-19T08:52:23.216349300Z][com.docker.diagnose.exe][I] (202e64de-6) 2dc18ba4-diagnose C->S Proxy GET /ping [2023-04-19T08:52:23.216875700Z][com.docker.diagnose.exe][W] (202e64de-6) 2dc18ba4-diagnose C<-S NoResponse GET /ping (526.4µs): Get "http://ipc/ping": open \.\pipe\dockerDesktopLinuxEngine: The system cannot find the file specified. [2023-04-19T08:52:24.228777300Z][com.docker.diagnose.exe][I] (202e64de-7) 2dc18ba4-diagnose C->S Proxy GET /ping [2023-04-19T08:52:24.231747500Z][com.docker.diagnose.exe][W] (202e64de-7) 2dc18ba4-diagnose C<-S NoResponse GET /ping (2.9702ms): Get "http://ipc/ping": open \.\pipe\dockerDesktopLinuxEngine: The system cannot find the file specified. [2023-04-19T08:52:25.241702200Z][com.docker.diagnose.exe][I] (202e64de-8) 2dc18ba4-diagnose C->S Proxy GET /ping [2023-04-19T08:52:25.241869300Z][com.docker.diagnose.exe][W] (202e64de-8) 2dc18ba4-diagnose C<-S NoResponse GET /ping (167.1µs): Get "http://ipc/ping": open \.\pipe\dockerDesktopLinuxEngine: The system cannot find the file specified.

[PASS] DD0006: is the Docker Desktop Service responding? [SKIP] DD0030: is the image access management authorized? [PASS] DD0033: does the host have Internet access? [PASS] DD0002: does the bootloader have virtualization enabled? [PASS] 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? [WARN] DD0024: is WSL installed? exit status 1 [WARN] DD0025: are WSL distros installed? exit status 1 [PASS] DD0026: is the WSL LxssManager service running? [WARN] DD0029: is the WSL 2 Linux filesystem corrupt? context deadline exceeded [WARN] DD0035: is the VM time synchronized? exit status 1 [PASS] DD0017: can a VM be started? [PASS] DD0016: is the LinuxKit VM running? [WARN] 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. [WARN] DD0004: is the Docker engine running? Get "http://ipc/docker": open \.\pipe\dockerLifecycleServer: The system cannot find the file specified. [PASS] DD0015: are the binary symlinks installed?

p1-0tr commented 1 year ago

@EoinLynch2 what version of WSL are you running (newer versions respond to wsl --version, but if it is an older one that's also useful info)? If you have not tried it yet, I would suggest updating WSL (wsl --update should do the trick).

EoinLynch2 commented 1 year ago

@p1-0tr

Output:

WSL version: 1.2.0.0 Kernel version: 5.15.90.1 WSLg version: 1.0.51 MSRDC version: 1.2.3770 Direct3D version: 1.608.2-61064218 DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp Windows version: 10.0.19045.2846 PS C:\Users\EoinLynch> wsl --update Checking for updates. The most recent version of Windows Subsystem for Linux is already installed.

p1-0tr commented 1 year ago

Hmm, that seems to be one of the most recent versions (I'm running the same), so I would expect the WSL hanging issue not to occur (IIRC versions at the end of last year exhibited that behaviour). I guess you could try installing WSL 1.1.3 (marked "latest" on the WSL github) - https://github.com/microsoft/WSL/releases/tag/1.1.3.

Just to confirm, when DD can't start, WSL commands become unresponsive, and you need to reboot (or kill wslservice.exe)?

EoinLynch2 commented 1 year ago

@p1-0tr Thanks for your swift reply. I will try that.

And yes, WSL commands become unresponsive... Although, killing the wslservice doesn't actually wake it up as it starts running again (DD starts it running again I would imagine)

EoinLynch2 commented 1 year ago

@p1-0tr No joy unfortunately. I also tried with the 2 more recent pre-release versions

ozzyknox commented 1 year ago

This is exactly my experience trying to get Docker Desktop to run properly on Windows 11. I wasted many days and eventually accepted that it doesn't work. Very poor because it is baked in as a default integration for many Windows based tools that work with docker like Visual Studio. I had to resort to using docker solely inside WSL Ubuntu and ignoring that it is actually running inside the Windows OS.

On Wed, 19 Apr 2023 at 13:36, EoinLynch2 @.***> wrote:

@p1-0tr https://github.com/p1-0tr No joy unfortunately. I also tried with the 2 more recent pre-release versions

— Reply to this email directly, view it on GitHub https://github.com/docker/for-win/issues/13184#issuecomment-1514578687, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABDM47DROI2OMYIMJL33ZZLXB7E3XANCNFSM6AAAAAAUCAZDPY . You are receiving this because you commented.Message ID: @.***>

p1-0tr commented 1 year ago

@p1-0tr No joy unfortunately. I also tried with the 2 more recent pre-release versions

@EoinLynch2 I'm sorry to hear that. If you are running a version of windows that supports HyperV switching DD to use that could be a workaround. To do that you'd need to change wslEngineEnabled to false in %APPDATA%/Docker/settings.json.

But if the WSL lockup issue is fully reproducible you could follow https://github.com/Microsoft/WSL/blob/master/CONTRIBUTING.md#8-collect-wsl-logs-recommended-method, to gather WSL diagnostics and create an issue.

EoinLynch2 commented 1 year ago

@p1-0tr Setting wslEngineEnabled seems to be working for me for now. I really appreciate you taking the time to help me with this. Thanks.

docker-robott commented 1 year ago

Closed issues are locked after 30 days of inactivity. This helps our team focus on active issues.

If you have found a problem that seems similar to this, please open a new issue.

/lifecycle locked