You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Docker Desktop doesn't start after upgrade to 4.1.0 #12229
Docker doesn't start after update to Docker Desktop 4.1.0
Expected behavior
Docker Desktop is running
Information
Please, help us understand the problem. For instance:
Is it reproducible? yes
Is the problem new? yes
Did the problem appear with an update? yes
A reproducible case if this is a bug, Dockerfiles with reproduction inside is best.
Windows Version: 21H1 (OS Build 19043.1237)
Docker Desktop Version: 4.1.0 (69386)
WSL2 or Hyper-V backend? WSL2
Are you running inside a virtualized Windows e.g. on a cloud server or a VM: no
Steps to reproduce the behavior
Update to Docker Desktop 4.1.0
Docker Desktop doesn't start after update
Reacted by soroshsabz, ptc-dday, omjadas, Arnaud Rocher, Felix Christl, Christopher Bailey, Joshua Sleeper, Patrício dos Santos, Fikri Muhammad Iqbal, Joona Heikkilä and 20 more
This could be the same problem with me, do docker system info work on Windows but not WSL? if yes then try to check the log from %AppData%\Local\Docker, if the logs are similar like this (can't access specified distro mount service: stat <some path> no such file or directory):
[03:56:35.873][IPCClient ][Info ] (c8e79548) d6596a4e-WslIntegrationService-CSharp C->S WSLCrossDistroService GET /check
[03:56:35.874][LinuxWSL2Engine ][Info ] msg="(c8e79548) 741b322b-cross-distro S<-C d6596a4e-WslIntegrationService-CSharp GET /check[[STACK]] at Docker.Engines.WslIntegrationService.<WaitForDistroReadyAsync>d__18.MoveNext() in C:\\workspaces\\master-merge\\src\\github.com\\docker\\pinata\\win\\src\\Docker.Engines\\WslIntegrationService.cs:line 0\n"
[03:56:35.874][LinuxWSL2Engine ][Error ] msg="(c8e79548) 741b322b-cross-distro S->C d6596a4e-WslIntegrationService-CSharp GET /check (144.296µs): can't access specified distro mount service: stat /run/guest-services/distro-services/arch.sock: no such file or directory[[STACK]]main.StartCrossDistroServer.func2({0xc0cf20, 0xc0000cd6c0})\n\t/go/src/github.com/docker/pinata/linuxkit/pkg/wsl-bootstrap/cross-distro-service.go:58 +0x412\n"
[03:56:36.137][IPCClient ][Info ] (4141d5b5) 5c844eaf-WslIntegrationService-CSharp C->S WSLCrossDistroService GET /check
[03:56:36.138][LinuxWSL2Engine ][Info ] msg="(4141d5b5) 741b322b-cross-distro S<-C 5c844eaf-WslIntegrationService-CSharp GET /check[[STACK]] at Docker.Engines.WslIntegrationService.<WaitForDistroReadyAsync>d__18.MoveNext() in C:\\workspaces\\master-merge\\src\\github.com\\docker\\pinata\\win\\src\\Docker.Engines\\WslIntegrationService.cs:line 0\n"
[03:56:36.138][LinuxWSL2Engine ][Error ] msg="(4141d5b5) 741b322b-cross-distro S->C 5c844eaf-WslIntegrationService-CSharp GET /check (128.005µs): can't access specified distro mount service: stat /run/guest-services/distro-services/arch.sock: no such file or directory[[STACK]]main.StartCrossDistroServer.func2({0xc0cf20, 0xc0000cd880})\n\t/go/src/github.com/docker/pinata/linuxkit/pkg/wsl-bootstrap/cross-distro-service.go:58 +0x412\n"
[03:56:36.407][IPCClient ][Info ] (47ed5f20) 4d75faee-WslIntegrationService-CSharp C->S WSLCrossDistroService GET /check
[03:56:36.407][LinuxWSL2Engine ][Info ] msg="(47ed5f20) 741b322b-cross-distro S<-C 4d75faee-WslIntegrationService-CSharp GET /check[[STACK]] at Docker.Engines.WslIntegrationService.<WaitForDistroReadyAsync>d__18.MoveNext() in C:\\workspaces\\master-merge\\src\\github.com\\docker\\pinata\\win\\src\\Docker.Engines\\WslIntegrationService.cs:line 0\n"
[03:56:36.408][LinuxWSL2Engine ][Error ] msg="(47ed5f20) 741b322b-cross-distro S->C 4d75faee-WslIntegrationService-CSharp GET /check (112.746µs): can't access specified distro mount service: stat /run/guest-services/distro-services/arch.sock: no such file or directory[[STACK]]main.StartCrossDistroServer.func2({0xc0cf20, 0xc0000cda40})\n\t/go/src/github.com/docker/pinata/linuxkit/pkg/wsl-bootstrap/cross-distro-service.go:58 +0x412\n"
[03:56:36.671][IPCClient ][Info ] (33b62031) 353aa777-WslIntegrationService-CSharp C->S WSLCrossDistroService GET /check
[03:56:36.672][LinuxWSL2Engine ][Info ] msg="(33b62031) 741b322b-cross-distro S<-C 353aa777-WslIntegrationService-CSharp GET /check[[STACK]] at Docker.Engines.WslIntegrationService.<WaitForDistroReadyAsync>d__18.MoveNext() in C:\\workspaces\\master-merge\\src\\github.com\\docker\\pinata\\win\\src\\Docker.Engines\\WslIntegrationService.cs:line 0\n"
[03:56:36.672][LinuxWSL2Engine ][Error ] msg="(33b62031) 741b322b-cross-distro S->C 353aa777-WslIntegrationService-CSharp GET /check (112.245µs): can't access specified distro mount service: stat /run/guest-services/distro-services/arch.sock: no such file or directory[[STACK]]main.StartCrossDistroServer.func2({0xc0cf20, 0xc0000cdc00})\n\t/go/src/github.com/docker/pinata/linuxkit/pkg/wsl-bootstrap/cross-distro-service.go:58 +0x412\n"
[03:56:36.936][IPCClient ][Info ] (b0594732) f83e1a63-WslIntegrationService-CSharp C->S WSLCrossDistroService GET /check
[03:56:36.937][LinuxWSL2Engine ][Info ] msg="(b0594732) 741b322b-cross-distro S<-C f83e1a63-WslIntegrationService-CSharp GET /check[[STACK]] at Docker.Engines.WslIntegrationService.<WaitForDistroReadyAsync>d__18.MoveNext() in C:\\workspaces\\master-merge\\src\\github.com\\docker\\pinata\\win\\src\\Docker.Engines\\WslIntegrationService.cs:line 0\n"
[03:56:36.937][LinuxWSL2Engine ][Info ] distro Arch mount service not running after 1m40.84157665s (no socket /run/guest-services/distro-services/arch.sock)
[03:56:36.937][LinuxWSL2Engine ][Error ] msg="(b0594732) 741b322b-cross-distro S->C f83e1a63-WslIntegrationService-CSharp GET /check (130.65µs): can't access specified distro mount service: stat /run/guest-services/distro-services/arch.sock: no such file or directory[[STACK]]main.StartCrossDistroServer.func2({0xc0cf20, 0xc0000cddc0})\n\t/go/src/github.com/docker/pinata/linuxkit/pkg/wsl-bootstrap/cross-distro-service.go:58 +0x412\n"
Then we are facing the same problem, Docker WSL Integration fails to start but the Docker engine is running with no problems, I don't know why this happens only with ArchWSL but not UbuntuWSL.
I tried resetting the Docker Desktop settings and I managed to disable the WSL Integration by unregistering ArchWSL and Docker Dekstop runs perfectly, but of course, I can't use Docker in ArchWSL because the WSL Integration is disabled, I tried enabling it again, restart then the same issue happens.
Docker engine runs normally and can be accessed from Windows. The only problem is, Docker Desktop Dashboard marks it as "Docker Engine is Starting" and I can't edit the settings to disable the WSL Integration, this is why I use the workarounds by unregistering ArchWSL to disable the WSL Integration, well even if I can disable the WSL Integration from the Docker Desktop Dashboard, I wouldn't do it because I need the WSL Integration.
Because of this, I'm forced to downgrade to Docker Desktop v4.0.1, and this issue doesn't exist in that version.
Reacted by Patrício dos Santos, Sanjay Rawat, Ben Cambourne, Ivan, Simon Koll, 机智的苏先锋 and hzmi
[16:02:11.274][LinuxWSL2Engine ][Info ] msg="(25939269) 66cb7c9b-cross-distro S<-C 3a15a164-WslIntegrationService-CSharp GET /check[[STACK]] at Docker.Engines.WslIntegrationService.<WaitForDistroReadyAsync>d__18.MoveNext() in C:\\workspaces\\master-merge\\src\\github.com\\docker\\pinata\\win\\src\\Docker.Engines\\WslIntegrationService.cs:line 0\n"
[16:02:11.274][LinuxWSL2Engine ][Info ] distro Arch mount service not running after 1.6�s (no socket /run/guest-services/distro-services/arch.sock)
[16:02:11.274][LinuxWSL2Engine ][Error ] msg="(25939269) 66cb7c9b-cross-distro S->C 3a15a164-WslIntegrationService-CSharp GET /check (238.5�s): can't access specified distro mount service: stat /run/guest-services/distro-services/arch.sock: no such file or directory[[STACK]]main.StartCrossDistroServer.func2({0xc0cf20, 0xc0003fe2a0})\n\t/go/src/github.com/docker/pinata/linuxkit/pkg/wsl-bootstrap/cross-distro-service.go:58 +0x412\n"
[16:02:11.574][GoBackendProcess ][Info ] msg="(c3977936) 86ed1b76-VMAPI S<-C 8c632b85-MetadataCMD GET /vm/init[[STACK]]github.com/docker/pinata/common/pkg/backend.(*backendClient).GetVMInit(0xc0003787a0)\n\t/go/src/github.com/docker/pinata/common/pkg/backend/client.go:126 +0x5a\nmain.getVMInit({0xb75ce0, 0xc0003787a0})\n\t/go/src/github.com/docker/pinata/linuxkit/pkg/metadata/main.go:39 +0xc6\nmain.main()\n\t/go/src/github.com/docker/pinata/linuxkit/pkg/metadata/main.go:27 +0x145\n"
Hmm, interesting. I think you should reference this issue on ArchWSL too.
Sorry that, I don't have the time right now to debug who and what caused this issue, so I don't have more info about why this is happening only on ArchWSL, I've only tested UbuntuWSL and I don't know if this happens with other WSL Distribution from MS Store or other wsldl-based WSL Distribution
OpenSuse WSL2 after update to 4.1 stuck on "Docker engine start" with this error in log:
[19:14:26.033][LinuxWSL2Engine ][Error ] msg="(6574522c) 608e1526-cross-distro S->C 9cbcdc3e-WslIntegrationService-CSharp GET /check (161.4µs): can't access specified distro mount service: stat /run/guest-services/distro-services/opensuse-tumbleweed.sock: no such file or directory[[STACK]]main.StartCrossDistroServer.func2({0xc0cf20, 0xc000110460})\n\t/go/src/github.com/docker/pinata/linuxkit/pkg/wsl-bootstrap/cross-distro-service.go:58 +0x412\n"
System.InvalidOperationException:
Failed to deploy distro docker-desktop to C:\Users\ssoroosh\AppData\Local\Docker\wsl\distro: exit code: -1
stdout: The network was not found.
stderr:
at Docker.ApiServices.WSL2.WslShortLivedCommandResult.LogAndThrowIfUnexpectedExitCode(String prefix, ILogger log, Int32 expectedExitCode) in C:\workspaces\master-merge\src\github.com\docker\pinata\win\src\Docker.ApiServices\WSL2\WslCommand.cs:line 146
at Docker.Engines.WSL2.WSL2Provisioning.<DeployDistroAsync>d__17.MoveNext() in C:\workspaces\master-merge\src\github.com\docker\pinata\win\src\Docker.Engines\WSL2\WSL2Provisioning.cs:line 168
--- 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.WSL2.WSL2Provisioning.<ProvisionAsync>d__8.MoveNext() in C:\workspaces\master-merge\src\github.com\docker\pinata\win\src\Docker.Engines\WSL2\WSL2Provisioning.cs:line 77
--- 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.WSL2.LinuxWSL2Engine.<DoStartAsync>d__29.MoveNext() in C:\workspaces\master-merge\src\github.com\docker\pinata\win\src\Docker.Engines\WSL2\LinuxWSL2Engine.cs:line 194
--- 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\master-merge\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__5.MoveNext() in C:\workspaces\master-merge\src\github.com\docker\pinata\win\src\Docker.ApiServices\StateMachines\StartTransition.cs:line 67
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at Docker.ApiServices.StateMachines.StartTransition.<DoRunAsync>d__5.MoveNext() in C:\workspaces\master-merge\src\github.com\docker\pinata\win\src\Docker.ApiServices\StateMachines\StartTransition.cs:line 92
This could be the same problem with me, do docker system info work on Windows but not WSL? if yes then try to check the log from %AppData%\Local\Docker, if the logs are similar like this (can't access specified distro mount service: stat <some path> no such file or directory):
[03:56:35.873][IPCClient ][Info ] (c8e79548) d6596a4e-WslIntegrationService-CSharp C->S WSLCrossDistroService GET /check
[03:56:35.874][LinuxWSL2Engine ][Info ] msg="(c8e79548) 741b322b-cross-distro S<-C d6596a4e-WslIntegrationService-CSharp GET /check[[STACK]] at Docker.Engines.WslIntegrationService.<WaitForDistroReadyAsync>d__18.MoveNext() in C:\\workspaces\\master-merge\\src\\github.com\\docker\\pinata\\win\\src\\Docker.Engines\\WslIntegrationService.cs:line 0\n"
[03:56:35.874][LinuxWSL2Engine ][Error ] msg="(c8e79548) 741b322b-cross-distro S->C d6596a4e-WslIntegrationService-CSharp GET /check (144.296µs): can't access specified distro mount service: stat /run/guest-services/distro-services/arch.sock: no such file or directory[[STACK]]main.StartCrossDistroServer.func2({0xc0cf20, 0xc0000cd6c0})\n\t/go/src/github.com/docker/pinata/linuxkit/pkg/wsl-bootstrap/cross-distro-service.go:58 +0x412\n"
[03:56:36.137][IPCClient ][Info ] (4141d5b5) 5c844eaf-WslIntegrationService-CSharp C->S WSLCrossDistroService GET /check
[03:56:36.138][LinuxWSL2Engine ][Info ] msg="(4141d5b5) 741b322b-cross-distro S<-C 5c844eaf-WslIntegrationService-CSharp GET /check[[STACK]] at Docker.Engines.WslIntegrationService.<WaitForDistroReadyAsync>d__18.MoveNext() in C:\\workspaces\\master-merge\\src\\github.com\\docker\\pinata\\win\\src\\Docker.Engines\\WslIntegrationService.cs:line 0\n"
[03:56:36.138][LinuxWSL2Engine ][Error ] msg="(4141d5b5) 741b322b-cross-distro S->C 5c844eaf-WslIntegrationService-CSharp GET /check (128.005µs): can't access specified distro mount service: stat /run/guest-services/distro-services/arch.sock: no such file or directory[[STACK]]main.StartCrossDistroServer.func2({0xc0cf20, 0xc0000cd880})\n\t/go/src/github.com/docker/pinata/linuxkit/pkg/wsl-bootstrap/cross-distro-service.go:58 +0x412\n"
[03:56:36.407][IPCClient ][Info ] (47ed5f20) 4d75faee-WslIntegrationService-CSharp C->S WSLCrossDistroService GET /check
[03:56:36.407][LinuxWSL2Engine ][Info ] msg="(47ed5f20) 741b322b-cross-distro S<-C 4d75faee-WslIntegrationService-CSharp GET /check[[STACK]] at Docker.Engines.WslIntegrationService.<WaitForDistroReadyAsync>d__18.MoveNext() in C:\\workspaces\\master-merge\\src\\github.com\\docker\\pinata\\win\\src\\Docker.Engines\\WslIntegrationService.cs:line 0\n"
[03:56:36.408][LinuxWSL2Engine ][Error ] msg="(47ed5f20) 741b322b-cross-distro S->C 4d75faee-WslIntegrationService-CSharp GET /check (112.746µs): can't access specified distro mount service: stat /run/guest-services/distro-services/arch.sock: no such file or directory[[STACK]]main.StartCrossDistroServer.func2({0xc0cf20, 0xc0000cda40})\n\t/go/src/github.com/docker/pinata/linuxkit/pkg/wsl-bootstrap/cross-distro-service.go:58 +0x412\n"
[03:56:36.671][IPCClient ][Info ] (33b62031) 353aa777-WslIntegrationService-CSharp C->S WSLCrossDistroService GET /check
[03:56:36.672][LinuxWSL2Engine ][Info ] msg="(33b62031) 741b322b-cross-distro S<-C 353aa777-WslIntegrationService-CSharp GET /check[[STACK]] at Docker.Engines.WslIntegrationService.<WaitForDistroReadyAsync>d__18.MoveNext() in C:\\workspaces\\master-merge\\src\\github.com\\docker\\pinata\\win\\src\\Docker.Engines\\WslIntegrationService.cs:line 0\n"
[03:56:36.672][LinuxWSL2Engine ][Error ] msg="(33b62031) 741b322b-cross-distro S->C 353aa777-WslIntegrationService-CSharp GET /check (112.245µs): can't access specified distro mount service: stat /run/guest-services/distro-services/arch.sock: no such file or directory[[STACK]]main.StartCrossDistroServer.func2({0xc0cf20, 0xc0000cdc00})\n\t/go/src/github.com/docker/pinata/linuxkit/pkg/wsl-bootstrap/cross-distro-service.go:58 +0x412\n"
[03:56:36.936][IPCClient ][Info ] (b0594732) f83e1a63-WslIntegrationService-CSharp C->S WSLCrossDistroService GET /check
[03:56:36.937][LinuxWSL2Engine ][Info ] msg="(b0594732) 741b322b-cross-distro S<-C f83e1a63-WslIntegrationService-CSharp GET /check[[STACK]] at Docker.Engines.WslIntegrationService.<WaitForDistroReadyAsync>d__18.MoveNext() in C:\\workspaces\\master-merge\\src\\github.com\\docker\\pinata\\win\\src\\Docker.Engines\\WslIntegrationService.cs:line 0\n"
[03:56:36.937][LinuxWSL2Engine ][Info ] distro Arch mount service not running after 1m40.84157665s (no socket /run/guest-services/distro-services/arch.sock)
[03:56:36.937][LinuxWSL2Engine ][Error ] msg="(b0594732) 741b322b-cross-distro S->C f83e1a63-WslIntegrationService-CSharp GET /check (130.65µs): can't access specified distro mount service: stat /run/guest-services/distro-services/arch.sock: no such file or directory[[STACK]]main.StartCrossDistroServer.func2({0xc0cf20, 0xc0000cddc0})\n\t/go/src/github.com/docker/pinata/linuxkit/pkg/wsl-bootstrap/cross-distro-service.go:58 +0x412\n"
Then we are facing the same problem, Docker WSL Integration fails to start but the Docker engine is running with no problems, I don't know why this happens only with ArchWSL but not UbuntuWSL. I tried resetting the Docker Desktop settings and I managed to disable the WSL Integration by unregistering ArchWSL and Docker Dekstop runs perfectly, but of course, I can't use Docker in ArchWSL because the WSL Integration is disabled, I tried enabling it again, restart then the same issue happens.
Docker engine runs normally and can be accessed from Windows. The only problem is, Docker Desktop Dashboard marks it as "Docker Engine is Starting" and I can't edit the settings to disable the WSL Integration, this is why I use the workarounds by unregistering ArchWSL to disable the WSL Integration, well even if I can disable the WSL Integration from the Docker Desktop Dashboard, I wouldn't do it because I need the WSL Integration.
Because of this, I'm forced to downgrade to Docker Desktop v4.0.1, and this issue doesn't exist in that version.
I tried to downgrade to 4.0.1, it didn't work for me, the same result. Downgrade to 4.0.0 worked for me.
Was able to get Docker Desktop 4.1.0 running successfully on Windows 11 by deleting all my WSL distros, then installing Docker Desktop 4.1.0. Then, when I have installed the distros again, Docker Desktop kept working.
Same issue here, after upgrading Docker Desktop from version 4.0.1 to version 4.1.0, using WSL2 with Debian.
In log.txt, under %UserProfile%\AppData\Local, the following line appears many times:
[20:55:15.535][LinuxWSL2Engine ][Error ] msg="(4fde6f80) 08d895e2-cross-distro S->C 28b46d0f-WslIntegrationService-CSharp GET /check (222µs): can't access specified distro mount service: stat /run/guest-services/distro-services/debian.sock: no such file or directory[[STACK]]main.StartCrossDistroServer.func2({0xc0cf20, 0xc000527420})\n\t/go/src/github.com/docker/pinata/linuxkit/pkg/wsl-bootstrap/cross-distro-service.go:58 +0x412\n"
I have the same problem with a Ubuntu WSL. Downgrading to 4.0.0 fixes the issue. Even disabling WSL integration prior to an upgrade does not solve the issue.
I tried following steps (Docker Desktop v4.1.0, Windows 10 21H1 build 19043.1237):
stop Docker Desktop if running (by killing its process if it is stuck starting)
backup WSL2 Debian filesystem with wsl.exe --export ... (PowerShell)
remove WSL2 Debian (uninstall the Windows app)
install WSL2 Debian again and start it to get a fresh install
start Docker Desktop ➜ ✔️ Success starting
getting a terminal in docker-desktop VM (docker run -it --rm --privileged --pid=host justincormack/nsenter1 in PowerShell), I can see that the /run/guests-services/distro-services/debian socket exists
stop Docker Desktop
extract original filesystem (backed up in step 1) with wsl.exe --import ... (PowerShell) in a temporary location
overwrite WSL Debian filesystem with the one extracted in step 7
I upgraded to 4.01 (Win10 with WSL2-Ubuntu) and now have an exception that prevents Docker Desktop from starting. Tried upgrading to Docker 4.1 and that didn't solve the problem, trying to go back to Docker 3.6
I tried running sudo /mnt/wsl/docker-desktop/docker-desktop-proxy --distro-name Debian --docker-desktop-root /mnt/wsl/docker-desktop, as I found in %UserProfile%\AppData\Roaming\Docker\log\host\com.docker.wsl-distro-proxy.exe.log. I get this result:
I’m closing this issue as 4.1.1 has been released, but feel free to keep discussing.
If you’re still having similar problems, please create a fresh issue.
Thanks!
Reacted by Jeff Sharp, Arnaud Rocher, Daniel Wagner and Christian Fosli
I’m closing this issue as 4.1.1 has been released, but feel free to keep discussing. If you’re still having similar problems, please create a fresh issue. Thanks!
Thanks, too! I can confirm resolution of this issue.
System.InvalidOperationException:
Failed to deploy distro docker-desktop to C:\Users\ssoroosh\AppData\Local\Docker\wsl\distro: exit code: -1
stdout: The network was not found.
stderr:
at Docker.ApiServices.WSL2.WslShortLivedCommandResult.LogAndThrowIfUnexpectedExitCode(String prefix, ILogger log, Int32 expectedExitCode) in C:\workspaces\PR-16599\src\github.com\docker\pinata\win\src\Docker.ApiServices\WSL2\WslCommand.cs:line 146
at Docker.Engines.WSL2.WSL2Provisioning.<DeployDistroAsync>d__17.MoveNext() in C:\workspaces\PR-16599\src\github.com\docker\pinata\win\src\Docker.Engines\WSL2\WSL2Provisioning.cs:line 168
--- 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.WSL2.WSL2Provisioning.<ProvisionAsync>d__8.MoveNext() in C:\workspaces\PR-16599\src\github.com\docker\pinata\win\src\Docker.Engines\WSL2\WSL2Provisioning.cs:line 77
--- 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.WSL2.LinuxWSL2Engine.<DoStartAsync>d__29.MoveNext() in C:\workspaces\PR-16599\src\github.com\docker\pinata\win\src\Docker.Engines\WSL2\LinuxWSL2Engine.cs:line 194
--- 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-16599\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__5.MoveNext() in C:\workspaces\PR-16599\src\github.com\docker\pinata\win\src\Docker.ApiServices\StateMachines\StartTransition.cs:line 67
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at Docker.ApiServices.StateMachines.StartTransition.<DoRunAsync>d__5.MoveNext() in C:\workspaces\PR-16599\src\github.com\docker\pinata\win\src\Docker.ApiServices\StateMachines\StartTransition.cs:line 92
Unregistering docker-desktop, and docker-desktop-data
Maybe also delete Local/Appdata/Docker
Just a precautions to also delete settings.json and set enableIntegrationWithDefaultWslDistro to false, and after it started up successfully, enable it from docker desktop app
Doing fine on Windows 11 build 22471.1000, ArchWSL Docker Desktop 4.1.1
Activity
Hazmi35 commentedon Oct 1, 2021
This could be the same problem with me, do
docker system infowork on Windows but not WSL? if yes then try to check the log from%AppData%\Local\Docker, if the logs are similar like this (can't access specified distro mount service: stat <some path> no such file or directory):Then we are facing the same problem, Docker WSL Integration fails to start but the Docker engine is running with no problems, I don't know why this happens only with ArchWSL but not UbuntuWSL.
I tried resetting the Docker Desktop settings and I managed to disable the WSL Integration by unregistering ArchWSL and Docker Dekstop runs perfectly, but of course, I can't use Docker in ArchWSL because the WSL Integration is disabled, I tried enabling it again, restart then the same issue happens.
Docker engine runs normally and can be accessed from Windows. The only problem is, Docker Desktop Dashboard marks it as "Docker Engine is Starting" and I can't edit the settings to disable the WSL Integration, this is why I use the workarounds by unregistering ArchWSL to disable the WSL Integration, well even if I can disable the WSL Integration from the Docker Desktop Dashboard, I wouldn't do it because I need the WSL Integration.
Because of this, I'm forced to downgrade to Docker Desktop v4.0.1, and this issue doesn't exist in that version.
danielwagn3r commentedon Oct 1, 2021
I'm using https://github.com/yuk7/ArchWSL , too.
Found following log entries:
Hazmi35 commentedon Oct 1, 2021
Hmm, interesting. I think you should reference this issue on ArchWSL too.
Sorry that, I don't have the time right now to debug who and what caused this issue, so I don't have more info about why this is happening only on ArchWSL, I've only tested UbuntuWSL and I don't know if this happens with other WSL Distribution from MS Store or other wsldl-based WSL Distribution
Thoth87 commentedon Oct 1, 2021
OpenSuse WSL2 after update to 4.1 stuck on "Docker engine start" with this error in log:
[19:14:26.033][LinuxWSL2Engine ][Error ] msg="(6574522c) 608e1526-cross-distro S->C 9cbcdc3e-WslIntegrationService-CSharp GET /check (161.4µs): can't access specified distro mount service: stat /run/guest-services/distro-services/opensuse-tumbleweed.sock: no such file or directory[[STACK]]main.StartCrossDistroServer.func2({0xc0cf20, 0xc000110460})\n\t/go/src/github.com/docker/pinata/linuxkit/pkg/wsl-bootstrap/cross-distro-service.go:58 +0x412\n"
soroshsabz commentedon Oct 1, 2021
I have the same error for WSL 2
yoanndelattre commentedon Oct 1, 2021
I have the same error for WSL 2
nbu commentedon Oct 2, 2021
I tried to downgrade to 4.0.1, it didn't work for me, the same result. Downgrade to 4.0.0 worked for me.
sharpjs commentedon Oct 2, 2021
Same issue here. Windows 11 Build 22000.194. Have ArchWSL. I'll unregister my ArchWSL until this is fixed.
nbu commentedon Oct 2, 2021
Was able to get Docker Desktop 4.1.0 running successfully on Windows 11 by deleting all my WSL distros, then installing Docker Desktop 4.1.0. Then, when I have installed the distros again, Docker Desktop kept working.
cailloumajor commentedon Oct 2, 2021
Same issue here, after upgrading Docker Desktop from version 4.0.1 to version 4.1.0, using WSL2 with Debian.
In
log.txt, under%UserProfile%\AppData\Local, the following line appears many times:fchristl commentedon Oct 2, 2021
I have the same problem with a Ubuntu WSL. Downgrading to 4.0.0 fixes the issue. Even disabling WSL integration prior to an upgrade does not solve the issue.
cailloumajor commentedon Oct 2, 2021
I tried following steps (Docker Desktop v4.1.0, Windows 10 21H1 build 19043.1237):
wsl.exe --export ...(PowerShell)docker run -it --rm --privileged --pid=host justincormack/nsenter1in PowerShell), I can see that the/run/guests-services/distro-services/debiansocket existswsl.exe --import ...(PowerShell) in a temporary location/run/guest-services/distro-servicesis not presentdrhoads commentedon Oct 2, 2021
I upgraded to 4.01 (Win10 with WSL2-Ubuntu) and now have an exception that prevents Docker Desktop from starting. Tried upgrading to Docker 4.1 and that didn't solve the problem, trying to go back to Docker 3.6
cailloumajor commentedon Oct 2, 2021
I tried running
sudo /mnt/wsl/docker-desktop/docker-desktop-proxy --distro-name Debian --docker-desktop-root /mnt/wsl/docker-desktop, as I found in%UserProfile%\AppData\Roaming\Docker\log\host\com.docker.wsl-distro-proxy.exe.log. I get this result:Trying the same command in a fresh Ubuntu WSL2 distro in which Docker runs well gives this result:
33 remaining items
mat007 commentedon Oct 12, 2021
I’m closing this issue as 4.1.1 has been released, but feel free to keep discussing.
If you’re still having similar problems, please create a fresh issue.
Thanks!
danielwagn3r commentedon Oct 12, 2021
Thanks, too! I can confirm resolution of this issue.
spullara commentedon Oct 13, 2021
This is happening to me with 4.1.1
[17:45:59.675][IPCClient ][Info ] (304b3aa4) 54f55d15-WslIntegrationService-CSharp C->S WSLCrossDistroService GET /check [17:46:00.660][VpnKitBridge ][Info ] msg="windows: still waiting for devenv-volumes, lifecycle-server, mutagen, volume-contents, debug-shell, docker, wsl2-cross-distro-service, wsl2-bootstrap-expose-ports, log, diagnosticd after 3h52m20.0002727s" [17:46:00.675][WslIntegrationService][Warning] HttpOS Client: connection timed out. [17:46:00.941][IPCClient ][Info ] (4556330a) 67183a94-WslIntegrationService-CSharp C->S WSLCrossDistroService GET /check [17:46:01.940][WslIntegrationService][Warning] HttpOS Client: connection timed out. [17:46:02.190][IPCClient ][Info ] (d42317f0) 270d7cf5-WslIntegrationService-CSharp C->S WSLCrossDistroService GET /check [17:46:03.190][WslIntegrationService][Warning] HttpOS Client: connection timed out. [17:46:03.441][IPCClient ][Info ] (cac06ccd) ee05e66f-WslIntegrationService-CSharp C->S WSLCrossDistroService GET /check [17:46:04.440][WslIntegrationService][Warning] HttpOS Client: connection timed out. [17:46:04.690][IPCClient ][Info ] (c8debfcd) 8dca372c-WslIntegrationService-CSharp C->S WSLCrossDistroService GET /check [17:46:05.690][WslIntegrationService][Warning] HttpOS Client: connection timed out. [17:46:05.941][IPCClient ][Info ] (92e8feeb) 4261ecf3-WslIntegrationService-CSharp C->S WSLCrossDistroService GET /check [17:46:06.940][WslIntegrationService][Warning] HttpOS Client: connection timed out. [17:46:07.190][IPCClient ][Info ] (e0ccbb65) 2c6ac634-WslIntegrationService-CSharp C->S WSLCrossDistroService GET /check [17:46:08.190][WslIntegrationService][Warning] HttpOS Client: connection timed out. [17:46:08.441][IPCClient ][Info ] (11b859c8) 918d9d81-WslIntegrationService-CSharp C->S WSLCrossDistroService GET /check [17:46:09.441][WslIntegrationService][Warning] HttpOS Client: connection timed out. [17:46:09.692][IPCClient ][Info ] (58443e0c) 5816662a-WslIntegrationService-CSharp C->S WSLCrossDistroService GET /check [17:46:10.660][VpnKitBridge ][Info ] msg="windows: still waiting for volume-contents, debug-shell, docker, wsl2-cross-distro-service, wsl2-bootstrap-expose-ports, devenv-volumes, lifecycle-server, mutagen, log, diagnosticd after 3h52m30.0007731s" [17:46:10.690][WslIntegrationService][Warning] HttpOS Client: connection timed out. [17:46:10.956][IPCClient ][Info ] (05bd4023) 650556ab-WslIntegrationService-CSharp C->S WSLCrossDistroService GET /check [17:46:11.955][WslIntegrationService][Warning] HttpOS Client: connection timed out. [17:46:12.205][IPCClient ][Info ] (40d55c18) 1ce536e2-WslIntegrationService-CSharp C->S WSLCrossDistroService GET /check [17:46:13.206][WslIntegrationService][Warning] HttpOS Client: connection timed out. [17:46:13.456][IPCClient ][Info ] (4761bdd4) ec8679f8-WslIntegrationService-CSharp C->S WSLCrossDistroService GET /check [17:46:14.456][WslIntegrationService][Warning] HttpOS Client: connection timed out. [17:46:14.707][IPCClient ][Info ] (2c6e0e06) 2f2ccfaa-WslIntegrationService-CSharp C->S WSLCrossDistroService GET /check [17:46:15.706][WslIntegrationService][Warning] HttpOS Client: connection timed out. [17:46:15.957][IPCClient ][Info ] (d3acbaeb) 4b443d5f-WslIntegrationService-CSharp C->S WSLCrossDistroService GET /check [17:46:16.956][WslIntegrationService][Warning] HttpOS Client: connection timed out.fmiqbal commentedon Oct 13, 2021
@spullara try my tips
spullara commentedon Oct 13, 2021
Those tips worked but it would be great if this was fixed without manual intervention. Can't imagine this will be great as everyone starts upgrading.
fmiqbal commentedon Oct 13, 2021
true that, which my tips basically mean, "clean install" docker desktop 4.1.1
soroshsabz commentedon Oct 14, 2021
@mat007 I have this problem in 4.1.1 too
mat007 commentedon Oct 14, 2021
@spullara @soroshsabz like I said: please open a fresh issue, and make sure to include diagnostics. Thanks!
soroshsabz commentedon Oct 14, 2021
@mat007 Ok, sorry, I create new issue as you wish, see #12270
soroshsabz commentedon Oct 14, 2021
related to microsoft/winget-pkgs#30328
orzazade commentedon Nov 6, 2021
thank you it worked for me.
docker-robott commentedon Dec 6, 2021
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.
Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle locked