search

docker / for-win

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

Problem with starting docker desktop in windows 10 #13306

Open bkcs2023 opened 1 year ago

bkcs2023 commented 1 year ago

Actual behavior

   An error occurred with System.InvalidOperationException: distro stopped unexpectedly

Expected behavior

   Starting docker desktop in windows 10

Information

I got an error message while starting docker desktop: System.InvalidOperationException: distro stopped unexpectedly at Docker.Engines.LinuxkitDaemonStartup.d5.MoveNext() in C:\workspaces\main-merges\src\github.com\docker\pinata\win\src\Docker.Engines\LinuxkitDaemonStartup.cs:line 60 --- 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.d28.MoveNext() in C:\workspaces\main-merges\src\github.com\docker\pinata\win\src\Docker.Engines\WSL2\LinuxWSL2Engine.cs:line 177 --- 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.d0.MoveNext() in C:\workspaces\main-merges\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.d5.MoveNext() in C:\workspaces\main-merges\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.d5.MoveNext() in C:\workspaces\main-merges\src\github.com\docker\pinata\win\src\Docker.ApiServices\StateMachines\StartTransition.cs:line 92 --- 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.d14.MoveNext() in C:\workspaces\main-merges\src\github.com\docker\pinata\win\src\Docker.ApiServices\StateMachines\EngineStateMachine.cs:line 69 --- 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.d__22.MoveNext() in C:\workspaces\main-merges\src\github.com\docker\pinata\win\src\Docker.Engines\Engines.cs:line 108

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

[PASS] DD0027: is there available disk space on the host? [FAIL] DD0028: is there available VM disk space? failed to retrieve the size information from '' [FAIL] DD0031: does the Docker API work? error during connect: This error may indicate that the docker daemon is not running.: 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. [FAIL] DD0004: is the Docker engine running? Get "http://ipc/docker": open \.\pipe\dockerLifecycleServer: The system cannot find the file specified. [2023-03-16T07:32:44.711048400Z][com.docker.diagnose.exe][I] ipc.NewClient: 4ae75c56-com.docker.diagnose -> \.\pipe\dockerLifecycleServer VMDockerdAPI [linuxkit/pkg/desktop-host-tools/pkg/client.NewClientForPath(...) [ linuxkit/pkg/desktop-host-tools/pkg/client/client.go:59 [linuxkit/pkg/desktop-host-tools/pkg/client.NewClient({0xdc5167, 0x13}) [ linuxkit/pkg/desktop-host-tools/pkg/client/client.go:53 +0x99 [common/pkg/diagkit/gather/diagnose.isDockerEngineRunning() [ common/pkg/diagkit/gather/diagnose/dockerd.go:21 +0x29 [common/pkg/diagkit/gather/diagnose.(*test).GetResult(0x134cde0) [ common/pkg/diagkit/gather/diagnose/test.go:46 +0x43 [common/pkg/diagkit/gather/diagnose.Run.func1(0x134cde0) [ common/pkg/diagkit/gather/diagnose/run.go:17 +0x5a [common/pkg/diagkit/gather/diagnose.walkOnce.func1(0xc22d77?, 0x134cde0) [ common/pkg/diagkit/gather/diagnose/run.go:140 +0x77 [common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x2, 0x134cde0, 0xc00035f728) [ common/pkg/diagkit/gather/diagnose/run.go:146 +0x36 [common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x1, 0x134ce60?, 0xc00035f728) [ common/pkg/diagkit/gather/diagnose/run.go:149 +0x73 [common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x0, 0xcb?, 0xc00035f728) [ common/pkg/diagkit/gather/diagnose/run.go:149 +0x73 [common/pkg/diagkit/gather/diagnose.walkOnce(0xd03a40?, 0xc00035f890) [ common/pkg/diagkit/gather/diagnose/run.go:135 +0xcc [common/pkg/diagkit/gather/diagnose.Run(0x134d5e0, 0x833f79d300000010?, {0xc00035fb20, 0x1, 0x1}) [ common/pkg/diagkit/gather/diagnose/run.go:16 +0x1ca [main.checkCmd({0xc00007a3d0?, 0xc00007a3d0?, 0x4?}, {0x0, 0x0}) [ common/cmd/com.docker.diagnose/main.go:133 +0x105 [main.main() [ common/cmd/com.docker.diagnose/main.go:99 +0x288 [2023-03-16T07:32:44.712610300Z][com.docker.diagnose.exe][I] (f7bdda07) 4ae75c56-com.docker.diagnose C->S VMDockerdAPI GET /docker [2023-03-16T07:32:44.713126400Z][com.docker.diagnose.exe][W] (f7bdda07) 4ae75c56-com.docker.diagnose C<-S NoResponse GET /docker (516.1µs): Get "http://ipc/docker": open \.\pipe\dockerLifecycleServer: The system cannot find the file specified. [2023-03-16T07:32:44.713126400Z][com.docker.diagnose.exe][I] (f7bdda07-1) 4ae75c56-com.docker.diagnose C->S VMDockerdAPI GET /ping [2023-03-16T07:32:44.713629800Z][com.docker.diagnose.exe][W] (f7bdda07-1) 4ae75c56-com.docker.diagnose C<-S NoResponse GET /ping (503.4µs): Get "http://ipc/ping": open \.\pipe\dockerLifecycleServer: The system cannot find the file specified. [2023-03-16T07:32:45.717728900Z][com.docker.diagnose.exe][I] (f7bdda07-2) 4ae75c56-com.docker.diagnose C->S VMDockerdAPI GET /ping [2023-03-16T07:32:45.718304900Z][com.docker.diagnose.exe][W] (f7bdda07-2) 4ae75c56-com.docker.diagnose C<-S NoResponse GET /ping (576µs): Get "http://ipc/ping": open \.\pipe\dockerLifecycleServer: The system cannot find the file specified. [2023-03-16T07:32:46.729808500Z][com.docker.diagnose.exe][I] (f7bdda07-3) 4ae75c56-com.docker.diagnose C->S VMDockerdAPI GET /ping [2023-03-16T07:32:46.730319400Z][com.docker.diagnose.exe][W] (f7bdda07-3) 4ae75c56-com.docker.diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \.\pipe\dockerLifecycleServer: The system cannot find the file specified. [2023-03-16T07:32:47.738609700Z][com.docker.diagnose.exe][I] (f7bdda07-4) 4ae75c56-com.docker.diagnose C->S VMDockerdAPI GET /ping [2023-03-16T07:32:47.738609700Z][com.docker.diagnose.exe][W] (f7bdda07-4) 4ae75c56-com.docker.diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \.\pipe\dockerLifecycleServer: The system cannot find the file specified. [2023-03-16T07:32:48.744942600Z][com.docker.diagnose.exe][I] (f7bdda07-5) 4ae75c56-com.docker.diagnose C->S VMDockerdAPI GET /ping [2023-03-16T07:32:48.744942600Z][com.docker.diagnose.exe][W] (f7bdda07-5) 4ae75c56-com.docker.diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \.\pipe\dockerLifecycleServer: The system cannot find the file specified. [2023-03-16T07:32:49.752538900Z][com.docker.diagnose.exe][I] (f7bdda07-6) 4ae75c56-com.docker.diagnose C->S VMDockerdAPI GET /ping [2023-03-16T07:32:49.752538900Z][com.docker.diagnose.exe][W] (f7bdda07-6) 4ae75c56-com.docker.diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \.\pipe\dockerLifecycleServer: The system cannot find the file specified. [2023-03-16T07:32:50.755250600Z][com.docker.diagnose.exe][I] (f7bdda07-7) 4ae75c56-com.docker.diagnose C->S VMDockerdAPI GET /ping [2023-03-16T07:32:50.755250600Z][com.docker.diagnose.exe][W] (f7bdda07-7) 4ae75c56-com.docker.diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \.\pipe\dockerLifecycleServer: The system cannot find the file specified. [2023-03-16T07:32:51.761862400Z][com.docker.diagnose.exe][I] (f7bdda07-8) 4ae75c56-com.docker.diagnose C->S VMDockerdAPI GET /ping [2023-03-16T07:32:51.762441300Z][com.docker.diagnose.exe][W] (f7bdda07-8) 4ae75c56-com.docker.diagnose C<-S NoResponse GET /ping (578.9µs): Get "http://ipc/ping": open \.\pipe\dockerLifecycleServer: The system cannot find the file specified.

[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-03-16T07:32:51.767107200Z][com.docker.diagnose.exe][I] ipc.NewClient: cc388f2e-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(0x134cd60) [ common/pkg/diagkit/gather/diagnose/test.go:46 +0x43 [common/pkg/diagkit/gather/diagnose.Run.func1(0x134cd60) [ common/pkg/diagkit/gather/diagnose/run.go:17 +0x5a [common/pkg/diagkit/gather/diagnose.walkOnce.func1(0xc22d77?, 0x134cd60) [ common/pkg/diagkit/gather/diagnose/run.go:140 +0x77 [common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x3, 0x134cd60, 0xc00059f728) [ common/pkg/diagkit/gather/diagnose/run.go:146 +0x36 [common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x2, 0x134cde0?, 0xc00059f728) [ common/pkg/diagkit/gather/diagnose/run.go:149 +0x73 [common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x1, 0x134ce60?, 0xc00059f728) [ common/pkg/diagkit/gather/diagnose/run.go:149 +0x73 [common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x0, 0xcb?, 0xc00059f728) [ common/pkg/diagkit/gather/diagnose/run.go:149 +0x73 [common/pkg/diagkit/gather/diagnose.walkOnce(0xd03a40?, 0xc00035f890) [ common/pkg/diagkit/gather/diagnose/run.go:135 +0xcc [common/pkg/diagkit/gather/diagnose.Run(0x134d5e0, 0x833f79d300000010?, {0xc00035fb20, 0x1, 0x1}) [ common/pkg/diagkit/gather/diagnose/run.go:16 +0x1ca [main.checkCmd({0xc00007a3d0?, 0xc00007a3d0?, 0x4?}, {0x0, 0x0}) [ common/cmd/com.docker.diagnose/main.go:133 +0x105 [main.main() [ common/cmd/com.docker.diagnose/main.go:99 +0x288 [2023-03-16T07:32:51.767623500Z][com.docker.diagnose.exe][I] (82ff0ef0) cc388f2e-diagnose C->S diagnosticsd GET /ping [2023-03-16T07:32:51.768137700Z][com.docker.diagnose.exe][W] (82ff0ef0) cc388f2e-diagnose C<-S NoResponse GET /ping (514.2µs): Get "http://ipc/ping": open \.\pipe\dockerDiagnosticd: The system cannot find the file specified.

[PASS] DD0016: is the LinuxKit VM running? [PASS] DD0001: is the application running? [SKIP] DD0018: does the host support virtualization? [PASS] DD0002: does the bootloader have virtualization enabled? [PASS] DD0017: can a VM be started? [PASS] DD0024: is WSL installed? [PASS] DD0021: is the WSL 2 Windows Feature enabled? [PASS] DD0022: is the Virtual Machine Platform Windows Feature enabled? [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] DD0015: are the binary symlinks installed? error during connect: This error may indicate that the docker daemon is not running.: 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] DD0013: is the $PATH ok? [PASS] DD0005: is the user in the docker-users group? [PASS] DD0007: is the backend responding? [FAIL] DD0014: are the backend processes running? 3 errors occurred:

[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-03-16T07:32:53.427861500Z][com.docker.diagnose.exe][I] ipc.NewClient: 49cb7ecf-diagnose -> \.\pipe\dockerDesktopLinuxEngine Proxy [common/pkg/diagkit/gather/diagnose.glob..func12() [ common/pkg/diagkit/gather/diagnose/ipc.go:91 +0x7a [common/pkg/diagkit/gather/diagnose.(*test).GetResult(0x134d2e0) [ common/pkg/diagkit/gather/diagnose/test.go:46 +0x43 [common/pkg/diagkit/gather/diagnose.Run.func1(0x134d2e0) [ common/pkg/diagkit/gather/diagnose/run.go:17 +0x5a [common/pkg/diagkit/gather/diagnose.walkOnce.func1(0x2?, 0x134d2e0) [ common/pkg/diagkit/gather/diagnose/run.go:140 +0x77 [common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x1, 0x134d2e0, 0xc00016d728) [ common/pkg/diagkit/gather/diagnose/run.go:146 +0x36 [common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x0, 0xcb?, 0xc00016d728) [ common/pkg/diagkit/gather/diagnose/run.go:149 +0x73 [common/pkg/diagkit/gather/diagnose.walkOnce(0xd03a40?, 0xc00035f890) [ common/pkg/diagkit/gather/diagnose/run.go:135 +0xcc [common/pkg/diagkit/gather/diagnose.Run(0x134d5e0, 0x833f79d300000010?, {0xc00035fb20, 0x1, 0x1}) [ common/pkg/diagkit/gather/diagnose/run.go:16 +0x1ca [main.checkCmd({0xc00007a3d0?, 0xc00007a3d0?, 0x4?}, {0x0, 0x0}) [ common/cmd/com.docker.diagnose/main.go:133 +0x105 [main.main() [ common/cmd/com.docker.diagnose/main.go:99 +0x288 [2023-03-16T07:32:53.427861500Z][com.docker.diagnose.exe][I] (ef5f6aef) 49cb7ecf-diagnose C->S Proxy GET /desktop-diagnostics/ping [2023-03-16T07:32:53.427861500Z][com.docker.diagnose.exe][W] (ef5f6aef) 49cb7ecf-diagnose C<-S NoResponse GET /desktop-diagnostics/ping (0s): Get "http://ipc/desktop-diagnostics/ping": open \.\pipe\dockerDesktopLinuxEngine: The system cannot find the file specified. [2023-03-16T07:32:53.428378900Z][com.docker.diagnose.exe][I] (ef5f6aef-1) 49cb7ecf-diagnose C->S Proxy GET /ping [2023-03-16T07:32:53.428378900Z][com.docker.diagnose.exe][W] (ef5f6aef-1) 49cb7ecf-diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \.\pipe\dockerDesktopLinuxEngine: The system cannot find the file specified. [2023-03-16T07:32:54.428579300Z][com.docker.diagnose.exe][I] (ef5f6aef-2) 49cb7ecf-diagnose C->S Proxy GET /ping [2023-03-16T07:32:54.428579300Z][com.docker.diagnose.exe][W] (ef5f6aef-2) 49cb7ecf-diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \.\pipe\dockerDesktopLinuxEngine: The system cannot find the file specified. [2023-03-16T07:32:55.435272400Z][com.docker.diagnose.exe][I] (ef5f6aef-3) 49cb7ecf-diagnose C->S Proxy GET /ping [2023-03-16T07:32:55.435272400Z][com.docker.diagnose.exe][W] (ef5f6aef-3) 49cb7ecf-diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \.\pipe\dockerDesktopLinuxEngine: The system cannot find the file specified. [2023-03-16T07:32:56.443056600Z][com.docker.diagnose.exe][I] (ef5f6aef-4) 49cb7ecf-diagnose C->S Proxy GET /ping [2023-03-16T07:32:56.443056600Z][com.docker.diagnose.exe][W] (ef5f6aef-4) 49cb7ecf-diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \.\pipe\dockerDesktopLinuxEngine: The system cannot find the file specified. [2023-03-16T07:32:57.446580000Z][com.docker.diagnose.exe][I] (ef5f6aef-5) 49cb7ecf-diagnose C->S Proxy GET /ping [2023-03-16T07:32:57.446580000Z][com.docker.diagnose.exe][W] (ef5f6aef-5) 49cb7ecf-diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \.\pipe\dockerDesktopLinuxEngine: The system cannot find the file specified. [2023-03-16T07:32:58.461118500Z][com.docker.diagnose.exe][I] (ef5f6aef-6) 49cb7ecf-diagnose C->S Proxy GET /ping [2023-03-16T07:32:58.461118500Z][com.docker.diagnose.exe][W] (ef5f6aef-6) 49cb7ecf-diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \.\pipe\dockerDesktopLinuxEngine: The system cannot find the file specified. [2023-03-16T07:32:59.475002300Z][com.docker.diagnose.exe][I] (ef5f6aef-7) 49cb7ecf-diagnose C->S Proxy GET /ping [2023-03-16T07:32:59.475002300Z][com.docker.diagnose.exe][W] (ef5f6aef-7) 49cb7ecf-diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \.\pipe\dockerDesktopLinuxEngine: The system cannot find the file specified. [2023-03-16T07:33:00.482141300Z][com.docker.diagnose.exe][I] (ef5f6aef-8) 49cb7ecf-diagnose C->S Proxy GET /ping [2023-03-16T07:33:00.482141300Z][com.docker.diagnose.exe][W] (ef5f6aef-8) 49cb7ecf-diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \.\pipe\dockerDesktopLinuxEngine: The system cannot find the file specified.

[PASS] DD0006: is the Docker Desktop Service responding? [FAIL] DD0012: is the VM networking working? network checks failed: Post "http://ipc/check-network-connectivity": open \.\pipe\dockerDiagnosticd: The system cannot find the file specified. [2023-03-16T07:33:00.524971500Z][com.docker.diagnose.exe][I] ipc.NewClient: fc575a8b-diagnose-network -> \.\pipe\dockerDiagnosticd diagnosticsd [common/pkg/diagkit/gather/diagnose.runIsVMNetworkingOK() [ common/pkg/diagkit/gather/diagnose/network.go:34 +0xd9 [common/pkg/diagkit/gather/diagnose.(*test).GetResult(0x134cfe0) [ common/pkg/diagkit/gather/diagnose/test.go:46 +0x43 [common/pkg/diagkit/gather/diagnose.Run.func1(0x134cfe0) [ common/pkg/diagkit/gather/diagnose/run.go:17 +0x5a [common/pkg/diagkit/gather/diagnose.walkOnce.func1(0x2?, 0x134cfe0) [ common/pkg/diagkit/gather/diagnose/run.go:140 +0x77 [common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x1, 0x134cfe0, 0xc00016d728) [ common/pkg/diagkit/gather/diagnose/run.go:146 +0x36 [common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x0, 0xcb?, 0xc00016d728) [ common/pkg/diagkit/gather/diagnose/run.go:149 +0x73 [common/pkg/diagkit/gather/diagnose.walkOnce(0xd03a40?, 0xc00035f890) [ common/pkg/diagkit/gather/diagnose/run.go:135 +0xcc [common/pkg/diagkit/gather/diagnose.Run(0x134d5e0, 0x833f79d300000010?, {0xc00035fb20, 0x1, 0x1}) [ common/pkg/diagkit/gather/diagnose/run.go:16 +0x1ca [main.checkCmd({0xc00007a3d0?, 0xc00007a3d0?, 0x4?}, {0x0, 0x0}) [ common/cmd/com.docker.diagnose/main.go:133 +0x105 [main.main() [ common/cmd/com.docker.diagnose/main.go:99 +0x288 [2023-03-16T07:33:00.524971500Z][com.docker.diagnose.exe][I] (b43d5d96) fc575a8b-diagnose-network C->S diagnosticsd POST /check-network-connectivity: {"ips":["143.248.14.189","172.26.208.1","172.25.160.1"]} [2023-03-16T07:33:00.525489600Z][com.docker.diagnose.exe][W] (b43d5d96) fc575a8b-diagnose-network C<-S NoResponse POST /check-network-connectivity (518.1µs): Post "http://ipc/check-network-connectivity": open \.\pipe\dockerDiagnosticd: The system cannot find the file specified. [2023-03-16T07:33:00.525489600Z][com.docker.diagnose.exe][I] (b43d5d96-1) fc575a8b-diagnose-network C->S diagnosticsd GET /ping [2023-03-16T07:33:00.525489600Z][com.docker.diagnose.exe][W] (b43d5d96-1) fc575a8b-diagnose-network C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \.\pipe\dockerDiagnosticd: The system cannot find the file specified. [2023-03-16T07:33:01.537333800Z][com.docker.diagnose.exe][I] (b43d5d96-2) fc575a8b-diagnose-network C->S diagnosticsd GET /ping [2023-03-16T07:33:01.537861600Z][com.docker.diagnose.exe][W] (b43d5d96-2) fc575a8b-diagnose-network C<-S NoResponse GET /ping (527.8µs): Get "http://ipc/ping": open \.\pipe\dockerDiagnosticd: The system cannot find the file specified. [2023-03-16T07:33:02.546603300Z][com.docker.diagnose.exe][I] (b43d5d96-3) fc575a8b-diagnose-network C->S diagnosticsd GET /ping [2023-03-16T07:33:02.546699700Z][com.docker.diagnose.exe][W] (b43d5d96-3) fc575a8b-diagnose-network C<-S NoResponse GET /ping (96.4µs): Get "http://ipc/ping": open \.\pipe\dockerDiagnosticd: The system cannot find the file specified. [2023-03-16T07:33:03.552362800Z][com.docker.diagnose.exe][I] (b43d5d96-4) fc575a8b-diagnose-network C->S diagnosticsd GET /ping [2023-03-16T07:33:03.552362800Z][com.docker.diagnose.exe][W] (b43d5d96-4) fc575a8b-diagnose-network C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \.\pipe\dockerDiagnosticd: The system cannot find the file specified. [2023-03-16T07:33:04.566044100Z][com.docker.diagnose.exe][I] (b43d5d96-5) fc575a8b-diagnose-network C->S diagnosticsd GET /ping [2023-03-16T07:33:04.566044100Z][com.docker.diagnose.exe][W] (b43d5d96-5) fc575a8b-diagnose-network C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \.\pipe\dockerDiagnosticd: The system cannot find the file specified. [2023-03-16T07:33:05.567123000Z][com.docker.diagnose.exe][I] (b43d5d96-6) fc575a8b-diagnose-network C->S diagnosticsd GET /ping [2023-03-16T07:33:05.567123000Z][com.docker.diagnose.exe][W] (b43d5d96-6) fc575a8b-diagnose-network C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \.\pipe\dockerDiagnosticd: The system cannot find the file specified. [2023-03-16T07:33:06.570585100Z][com.docker.diagnose.exe][I] (b43d5d96-7) fc575a8b-diagnose-network C->S diagnosticsd GET /ping [2023-03-16T07:33:06.571164000Z][com.docker.diagnose.exe][W] (b43d5d96-7) fc575a8b-diagnose-network C<-S NoResponse GET /ping (578.9µs): Get "http://ipc/ping": open \.\pipe\dockerDiagnosticd: The system cannot find the file specified. [2023-03-16T07:33:07.582727900Z][com.docker.diagnose.exe][I] (b43d5d96-8) fc575a8b-diagnose-network C->S diagnosticsd GET /ping [2023-03-16T07:33:07.582727900Z][com.docker.diagnose.exe][W] (b43d5d96-8) fc575a8b-diagnose-network C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \.\pipe\dockerDiagnosticd: The system cannot find the file specified.

[FAIL] DD0032: do Docker networks overlap with host IPs? error during connect: This error may indicate that the docker daemon is not running.: Get "http://%2F%2F.%2Fpipe%2Fdocker_engine_linux/v1.24/networks": open //./pipe/docker_engine_linux: The system cannot find the file specified. [SKIP] DD0030: is the image access management authorized? [PASS] DD0033: does the host have Internet access?

Please investigate the following 4 issues:

1 : The test: are the backend processes running? Failed with: 3 errors occurred:

Not all of the backend processes are running.

2 : The test: is the VM networking working? Failed with: network checks failed: Post "http://ipc/check-network-connectivity": open \.\pipe\dockerDiagnosticd: The system cannot find the file specified.

VM seems to have a network connectivity issue. Please check your host firewall and anti-virus settings in case they are blocking the VM.

3 : The test: is there available VM disk space? Failed with: failed to retrieve the size information from ''

Verify the available VM disk space. Try running docker system prune to clean up.

4 : The test: are the LinuxKit services running? Failed with: failed to ping VM diagnosticsd with error: Get "http://ipc/ping": open \.\pipe\dockerDiagnosticd: The system cannot find the file specified.

The Docker engine runs inside a Linux VM as a service. Therefore the services must have started.

iluvnepal commented 1 year ago

Error response from daemon: open \\.\pipe\docker_engine_linux: The system cannot find the file specified. This happened to me when running sqlserver in docker to persist generated test data. Particularly when the database was full. As long as i was clearing data and repopulating it, it was alright. Then once, i randomly stopped the container when it was still full to the limit, then it could not start the container anymore saying some memory problem. I restarted docker but it just keeps loading and never finishes. Havent solved it yet. Tyring new installation next.