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
I have tried with the latest version of Docker Desktop
I have tried disabling enabled experimental features
I have uploaded Diagnostics
Diagnostics ID:
Actual behavior
After version update to 4.15.0 (93002) Docker Desktop hangs on "Engine starting", cannot update (screen shows a loading icon)
Expected behavior
Normal operation
Information
Windows Version:
Docker Desktop Version:
WSL2 or Hyper-V backend?
Are you running inside a virtualized Windows e.g. on a cloud server or a VM:
Output of & "C:\Program Files\Docker\Docker\resources\com.docker.diagnose.exe" check
[2023-04-02T07:39:22.641770900Z][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?
[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-02T07:39:30.204954700Z][com.docker.diagnose.exe][I] ipc.NewClient: 855070d3-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(0x1c940c0)
[ common/pkg/diagkit/gather/diagnose/test.go:46 +0x43
[common/pkg/diagkit/gather/diagnose.Run.func1(0x1c940c0)
[ common/pkg/diagkit/gather/diagnose/run.go:17 +0x5a
[common/pkg/diagkit/gather/diagnose.walkOnce.func1(0x4?, 0x1c940c0)
[ common/pkg/diagkit/gather/diagnose/run.go:142 +0x77
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x3, 0x1c940c0, 0xc00022f728)
[ common/pkg/diagkit/gather/diagnose/run.go:151 +0x87
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x2, 0x1c94140, 0xc00022f728)
[ common/pkg/diagkit/gather/diagnose/run.go:148 +0x52
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x1, 0x1c941c0, 0xc00022f728)
[ common/pkg/diagkit/gather/diagnose/run.go:148 +0x52
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x0, 0x1c94940, 0xc00022f728)
[ common/pkg/diagkit/gather/diagnose/run.go:148 +0x52
[common/pkg/diagkit/gather/diagnose.walkOnce(0x1632c80?, 0xc00035f890)
[ common/pkg/diagkit/gather/diagnose/run.go:137 +0xcc
[common/pkg/diagkit/gather/diagnose.Run(0x1c94940, 0x321e669500000010?, {0xc00035fb20, 0x1, 0x1})
[ common/pkg/diagkit/gather/diagnose/run.go:16 +0x1d4
[main.checkCmd({0xc0001163b0?, 0xc0001163b0?, 0x4?}, {0x0, 0x0})
[ common/cmd/com.docker.diagnose/main.go:133 +0x105
[main.main()
[ common/cmd/com.docker.diagnose/main.go:99 +0x287
[2023-04-02T07:39:30.205487300Z][com.docker.diagnose.exe][I] (1afa7504) 855070d3-diagnose C->S diagnosticsd GET /ping
[2023-04-02T07:39:30.205487300Z][com.docker.diagnose.exe][W] (1afa7504) 855070d3-diagnose C<-S NoResponse GET /ping (0s): 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-02T07:39:30.206529600Z][com.docker.diagnose.exe][I] ipc.NewClient: 801d1e13-com.docker.diagnose -> \.\pipe\dockerLifecycleServer VMDockerdAPI
[linuxkit/pkg/desktop-host-tools/pkg/client.NewClientForPath(...)
[ linuxkit/pkg/desktop-host-tools/pkg/client/client.go:61
[linuxkit/pkg/desktop-host-tools/pkg/client.NewClient({0x16f68bf, 0x13})
[ linuxkit/pkg/desktop-host-tools/pkg/client/client.go:55 +0x99
[common/pkg/diagkit/gather/diagnose.isDockerEngineRunning()
[ common/pkg/diagkit/gather/diagnose/dockerd.go:21 +0x29
[common/pkg/diagkit/gather/diagnose.(*test).GetResult(0x1c94140)
[ common/pkg/diagkit/gather/diagnose/test.go:46 +0x43
[common/pkg/diagkit/gather/diagnose.Run.func1(0x1c94140)
[ common/pkg/diagkit/gather/diagnose/run.go:17 +0x5a
[common/pkg/diagkit/gather/diagnose.walkOnce.func1(0x3?, 0x1c94140)
[ common/pkg/diagkit/gather/diagnose/run.go:142 +0x77
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x2, 0x1c94140, 0xc00022f728)
[ common/pkg/diagkit/gather/diagnose/run.go:151 +0x87
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x1, 0x1c941c0, 0xc00022f728)
[ common/pkg/diagkit/gather/diagnose/run.go:148 +0x52
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x0, 0x1c94940, 0xc00022f728)
[ common/pkg/diagkit/gather/diagnose/run.go:148 +0x52
[common/pkg/diagkit/gather/diagnose.walkOnce(0x1632c80?, 0xc00035f890)
[ common/pkg/diagkit/gather/diagnose/run.go:137 +0xcc
[common/pkg/diagkit/gather/diagnose.Run(0x1c94940, 0x321e669500000010?, {0xc00035fb20, 0x1, 0x1})
[ common/pkg/diagkit/gather/diagnose/run.go:16 +0x1d4
[main.checkCmd({0xc0001163b0?, 0xc0001163b0?, 0x4?}, {0x0, 0x0})
[ common/cmd/com.docker.diagnose/main.go:133 +0x105
[main.main()
[ common/cmd/com.docker.diagnose/main.go:99 +0x287
[2023-04-02T07:39:30.207051400Z][com.docker.diagnose.exe][I] (471e8550) 801d1e13-com.docker.diagnose C->S VMDockerdAPI GET /docker
[2023-04-02T07:39:30.207573000Z][com.docker.diagnose.exe][W] (471e8550) 801d1e13-com.docker.diagnose C<-S NoResponse GET /docker (521.6µs): Get "http://ipc/docker": open \.\pipe\dockerLifecycleServer: The system cannot find the file specified.
[2023-04-02T07:39:30.208096500Z][com.docker.diagnose.exe][I] (471e8550-1) 801d1e13-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-04-02T07:39:30.208096500Z][com.docker.diagnose.exe][W] (471e8550-1) 801d1e13-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-02T07:39:31.221209900Z][com.docker.diagnose.exe][I] (471e8550-2) 801d1e13-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-04-02T07:39:31.221714100Z][com.docker.diagnose.exe][W] (471e8550-2) 801d1e13-com.docker.diagnose C<-S NoResponse GET /ping (504.2µs): Get "http://ipc/ping": open \.\pipe\dockerLifecycleServer: The system cannot find the file specified.
[2023-04-02T07:39:32.228354800Z][com.docker.diagnose.exe][I] (471e8550-3) 801d1e13-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-04-02T07:39:32.228354800Z][com.docker.diagnose.exe][W] (471e8550-3) 801d1e13-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-02T07:39:33.242757600Z][com.docker.diagnose.exe][I] (471e8550-4) 801d1e13-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-04-02T07:39:33.242757600Z][com.docker.diagnose.exe][W] (471e8550-4) 801d1e13-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-02T07:39:34.244385900Z][com.docker.diagnose.exe][I] (471e8550-5) 801d1e13-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-04-02T07:39:34.244466900Z][com.docker.diagnose.exe][W] (471e8550-5) 801d1e13-com.docker.diagnose C<-S NoResponse GET /ping (81µs): Get "http://ipc/ping": open \.\pipe\dockerLifecycleServer: The system cannot find the file specified.
[2023-04-02T07:39:35.257731800Z][com.docker.diagnose.exe][I] (471e8550-6) 801d1e13-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-04-02T07:39:35.257731800Z][com.docker.diagnose.exe][W] (471e8550-6) 801d1e13-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-02T07:39:36.271020400Z][com.docker.diagnose.exe][I] (471e8550-7) 801d1e13-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-04-02T07:39:36.271531700Z][com.docker.diagnose.exe][W] (471e8550-7) 801d1e13-com.docker.diagnose C<-S NoResponse GET /ping (511.3µs): Get "http://ipc/ping": open \.\pipe\dockerLifecycleServer: The system cannot find the file specified.
[2023-04-02T07:39:37.272654500Z][com.docker.diagnose.exe][I] (471e8550-8) 801d1e13-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-04-02T07:39:37.272654500Z][com.docker.diagnose.exe][W] (471e8550-8) 801d1e13-com.docker.diagnose C<-S NoResponse GET /ping (0s): 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: 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.
[PASS] DD0013: is the $PATH ok?
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
[FAIL] DD0005: is the user in the docker-users group? The user name could not be found.
[FAIL] DD0014: are the backend processes running? 4 errors occurred:
* com.docker.proxy.exe is not running
* com.docker.wsl-distro-proxy.exe is not running
* vpnkit-bridge.exe is not running
* com.docker.vpnkit.exe is not running
[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-02T07:39:41.310149700Z][com.docker.diagnose.exe][I] ipc.NewClient: dbbd364b-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(0x1c94640)
[ common/pkg/diagkit/gather/diagnose/test.go:46 +0x43
[common/pkg/diagkit/gather/diagnose.Run.func1(0x1c94640)
[ common/pkg/diagkit/gather/diagnose/run.go:17 +0x5a
[common/pkg/diagkit/gather/diagnose.walkOnce.func1(0x2?, 0x1c94640)
[ common/pkg/diagkit/gather/diagnose/run.go:142 +0x77
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x1, 0x1c94640, 0xc00023b728)
[ common/pkg/diagkit/gather/diagnose/run.go:151 +0x87
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x0, 0x1c94940, 0xc00023b728)
[ common/pkg/diagkit/gather/diagnose/run.go:148 +0x52
[common/pkg/diagkit/gather/diagnose.walkOnce(0x1632c80?, 0xc00035f890)
[ common/pkg/diagkit/gather/diagnose/run.go:137 +0xcc
[common/pkg/diagkit/gather/diagnose.Run(0x1c94940, 0x321e669500000010?, {0xc00035fb20, 0x1, 0x1})
[ common/pkg/diagkit/gather/diagnose/run.go:16 +0x1d4
[main.checkCmd({0xc0001163b0?, 0xc0001163b0?, 0x4?}, {0x0, 0x0})
[ common/cmd/com.docker.diagnose/main.go:133 +0x105
[main.main()
[ common/cmd/com.docker.diagnose/main.go:99 +0x287
[2023-04-02T07:39:41.310149700Z][com.docker.diagnose.exe][I] (0040d23c) dbbd364b-diagnose C->S Proxy GET /desktop-diagnostics/ping
[2023-04-02T07:39:41.310717600Z][com.docker.diagnose.exe][W] (0040d23c) dbbd364b-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-04-02T07:39:41.311248200Z][com.docker.diagnose.exe][I] (0040d23c-1) dbbd364b-diagnose C->S Proxy GET /ping
[2023-04-02T07:39:41.311312200Z][com.docker.diagnose.exe][W] (0040d23c-1) dbbd364b-diagnose C<-S NoResponse GET /ping (64µs): Get "http://ipc/ping": open \.\pipe\dockerDesktopLinuxEngine: The system cannot find the file specified.
[2023-04-02T07:39:42.323066600Z][com.docker.diagnose.exe][I] (0040d23c-2) dbbd364b-diagnose C->S Proxy GET /ping
[2023-04-02T07:39:42.323066600Z][com.docker.diagnose.exe][W] (0040d23c-2) dbbd364b-diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \.\pipe\dockerDesktopLinuxEngine: The system cannot find the file specified.
[2023-04-02T07:39:43.324194600Z][com.docker.diagnose.exe][I] (0040d23c-3) dbbd364b-diagnose C->S Proxy GET /ping
[2023-04-02T07:39:43.324194600Z][com.docker.diagnose.exe][W] (0040d23c-3) dbbd364b-diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \.\pipe\dockerDesktopLinuxEngine: The system cannot find the file specified.
[2023-04-02T07:39:44.337274000Z][com.docker.diagnose.exe][I] (0040d23c-4) dbbd364b-diagnose C->S Proxy GET /ping
[2023-04-02T07:39:44.337274000Z][com.docker.diagnose.exe][W] (0040d23c-4) dbbd364b-diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \.\pipe\dockerDesktopLinuxEngine: The system cannot find the file specified.
[2023-04-02T07:39:45.352112600Z][com.docker.diagnose.exe][I] (0040d23c-5) dbbd364b-diagnose C->S Proxy GET /ping
[2023-04-02T07:39:45.352112600Z][com.docker.diagnose.exe][W] (0040d23c-5) dbbd364b-diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \.\pipe\dockerDesktopLinuxEngine: The system cannot find the file specified.
[2023-04-02T07:39:46.352958900Z][com.docker.diagnose.exe][I] (0040d23c-6) dbbd364b-diagnose C->S Proxy GET /ping
[2023-04-02T07:39:46.353514200Z][com.docker.diagnose.exe][W] (0040d23c-6) dbbd364b-diagnose C<-S NoResponse GET /ping (555.3µs): Get "http://ipc/ping": open \.\pipe\dockerDesktopLinuxEngine: The system cannot find the file specified.
[2023-04-02T07:39:47.353657600Z][com.docker.diagnose.exe][I] (0040d23c-7) dbbd364b-diagnose C->S Proxy GET /ping
[2023-04-02T07:39:47.353657600Z][com.docker.diagnose.exe][W] (0040d23c-7) dbbd364b-diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \.\pipe\dockerDesktopLinuxEngine: The system cannot find the file specified.
[2023-04-02T07:39:48.368806900Z][com.docker.diagnose.exe][I] (0040d23c-8) dbbd364b-diagnose C->S Proxy GET /ping
[2023-04-02T07:39:48.368806900Z][com.docker.diagnose.exe][W] (0040d23c-8) dbbd364b-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-04-02T07:39:48.455336800Z][com.docker.diagnose.exe][I] ipc.NewClient: 5cac3ff2-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(0x1c94340)
[ common/pkg/diagkit/gather/diagnose/test.go:46 +0x43
[common/pkg/diagkit/gather/diagnose.Run.func1(0x1c94340)
[ common/pkg/diagkit/gather/diagnose/run.go:17 +0x5a
[common/pkg/diagkit/gather/diagnose.walkOnce.func1(0x2?, 0x1c94340)
[ common/pkg/diagkit/gather/diagnose/run.go:142 +0x77
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x1, 0x1c94340, 0xc00023b728)
[ common/pkg/diagkit/gather/diagnose/run.go:151 +0x87
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x0, 0x1c94940, 0xc00023b728)
[ common/pkg/diagkit/gather/diagnose/run.go:148 +0x52
[common/pkg/diagkit/gather/diagnose.walkOnce(0x1632c80?, 0xc00035f890)
[ common/pkg/diagkit/gather/diagnose/run.go:137 +0xcc
[common/pkg/diagkit/gather/diagnose.Run(0x1c94940, 0x321e669500000010?, {0xc00035fb20, 0x1, 0x1})
[ common/pkg/diagkit/gather/diagnose/run.go:16 +0x1d4
[main.checkCmd({0xc0001163b0?, 0xc0001163b0?, 0x4?}, {0x0, 0x0})
[ common/cmd/com.docker.diagnose/main.go:133 +0x105
[main.main()
[ common/cmd/com.docker.diagnose/main.go:99 +0x287
[2023-04-02T07:39:48.455839900Z][com.docker.diagnose.exe][I] (97baece1) 5cac3ff2-diagnose-network C->S diagnosticsd POST /check-network-connectivity: {"ips":["192.168.0.108","100.64.248.170","172.20.224.1","172.18.176.1"]}
[2023-04-02T07:39:48.455839900Z][com.docker.diagnose.exe][W] (97baece1) 5cac3ff2-diagnose-network C<-S NoResponse POST /check-network-connectivity (503.1µs): Post "http://ipc/check-network-connectivity": open \.\pipe\dockerDiagnosticd: The system cannot find the file specified.
[2023-04-02T07:39:48.456355200Z][com.docker.diagnose.exe][I] (97baece1-1) 5cac3ff2-diagnose-network C->S diagnosticsd GET /ping
[2023-04-02T07:39:48.456355200Z][com.docker.diagnose.exe][W] (97baece1-1) 5cac3ff2-diagnose-network C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \.\pipe\dockerDiagnosticd: The system cannot find the file specified.
[2023-04-02T07:39:49.459203800Z][com.docker.diagnose.exe][I] (97baece1-2) 5cac3ff2-diagnose-network C->S diagnosticsd GET /ping
[2023-04-02T07:39:49.459203800Z][com.docker.diagnose.exe][W] (97baece1-2) 5cac3ff2-diagnose-network C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \.\pipe\dockerDiagnosticd: The system cannot find the file specified.
[2023-04-02T07:39:50.468895800Z][com.docker.diagnose.exe][I] (97baece1-3) 5cac3ff2-diagnose-network C->S diagnosticsd GET /ping
[2023-04-02T07:39:50.468895800Z][com.docker.diagnose.exe][W] (97baece1-3) 5cac3ff2-diagnose-network C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \.\pipe\dockerDiagnosticd: The system cannot find the file specified.
[2023-04-02T07:39:51.481628400Z][com.docker.diagnose.exe][I] (97baece1-4) 5cac3ff2-diagnose-network C->S diagnosticsd GET /ping
[2023-04-02T07:39:51.481628400Z][com.docker.diagnose.exe][W] (97baece1-4) 5cac3ff2-diagnose-network C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \.\pipe\dockerDiagnosticd: The system cannot find the file specified.
[2023-04-02T07:39:52.493499200Z][com.docker.diagnose.exe][I] (97baece1-5) 5cac3ff2-diagnose-network C->S diagnosticsd GET /ping
[2023-04-02T07:39:52.493499200Z][com.docker.diagnose.exe][W] (97baece1-5) 5cac3ff2-diagnose-network C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \.\pipe\dockerDiagnosticd: The system cannot find the file specified.
[2023-04-02T07:39:53.508019400Z][com.docker.diagnose.exe][I] (97baece1-6) 5cac3ff2-diagnose-network C->S diagnosticsd GET /ping
[2023-04-02T07:39:53.508019400Z][com.docker.diagnose.exe][W] (97baece1-6) 5cac3ff2-diagnose-network C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \.\pipe\dockerDiagnosticd: The system cannot find the file specified.
[2023-04-02T07:39:54.517121400Z][com.docker.diagnose.exe][I] (97baece1-7) 5cac3ff2-diagnose-network C->S diagnosticsd GET /ping
[2023-04-02T07:39:54.517121400Z][com.docker.diagnose.exe][W] (97baece1-7) 5cac3ff2-diagnose-network C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \.\pipe\dockerDiagnosticd: The system cannot find the file specified.
[2023-04-02T07:39:55.528965900Z][com.docker.diagnose.exe][I] (97baece1-8) 5cac3ff2-diagnose-network C->S diagnosticsd GET /ping
[2023-04-02T07:39:55.528965900Z][com.docker.diagnose.exe][W] (97baece1-8) 5cac3ff2-diagnose-network C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \.\pipe\dockerDiagnosticd: The system cannot find the file specified.
[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?
[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?
[WARN] 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.
[WARN] 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.
Please note the following 4 warnings:
1 : The check: are the LinuxKit services running?
Produced the following warning: 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.
2 : The check: is the Docker engine running?
Produced the following warning: Get "http://ipc/docker": open \.\pipe\dockerLifecycleServer: The system cannot find the file specified.
The Docker engine manages all containers and images on the host. Check the dockerd.log to see why it failed to start.
3 : The check: does the Docker API work?
Produced the following warning: 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.
If the Docker API is not available from the host then Docker Desktop will not work correctly.
4 : The check: do Docker networks overlap with host IPs?
Produced the following warning: 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.
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.
1 : The test: are the backend processes running?
Failed with: 4 errors occurred:
* com.docker.proxy.exe is not running
* com.docker.wsl-distro-proxy.exe is not running
* vpnkit-bridge.exe is not running
* com.docker.vpnkit.exe is not running
Not all of the backend processes are running.
Steps to reproduce the behavior
...
...
The text was updated successfully, but these errors were encountered:
Actual behavior
After version update to 4.15.0 (93002) Docker Desktop hangs on "Engine starting", cannot update (screen shows a loading icon)
Expected behavior
Normal operation
Information
Output of
& "C:\Program Files\Docker\Docker\resources\com.docker.diagnose.exe" check[2023-04-02T07:39:22.641770900Z][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?
[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-02T07:39:30.204954700Z][com.docker.diagnose.exe][I] ipc.NewClient: 855070d3-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(0x1c940c0)
[ common/pkg/diagkit/gather/diagnose/test.go:46 +0x43
[common/pkg/diagkit/gather/diagnose.Run.func1(0x1c940c0)
[ common/pkg/diagkit/gather/diagnose/run.go:17 +0x5a
[common/pkg/diagkit/gather/diagnose.walkOnce.func1(0x4?, 0x1c940c0)
[ common/pkg/diagkit/gather/diagnose/run.go:142 +0x77
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x3, 0x1c940c0, 0xc00022f728)
[ common/pkg/diagkit/gather/diagnose/run.go:151 +0x87
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x2, 0x1c94140, 0xc00022f728)
[ common/pkg/diagkit/gather/diagnose/run.go:148 +0x52
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x1, 0x1c941c0, 0xc00022f728)
[ common/pkg/diagkit/gather/diagnose/run.go:148 +0x52
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x0, 0x1c94940, 0xc00022f728)
[ common/pkg/diagkit/gather/diagnose/run.go:148 +0x52
[common/pkg/diagkit/gather/diagnose.walkOnce(0x1632c80?, 0xc00035f890)
[ common/pkg/diagkit/gather/diagnose/run.go:137 +0xcc
[common/pkg/diagkit/gather/diagnose.Run(0x1c94940, 0x321e669500000010?, {0xc00035fb20, 0x1, 0x1})
[ common/pkg/diagkit/gather/diagnose/run.go:16 +0x1d4
[main.checkCmd({0xc0001163b0?, 0xc0001163b0?, 0x4?}, {0x0, 0x0})
[ common/cmd/com.docker.diagnose/main.go:133 +0x105
[main.main()
[ common/cmd/com.docker.diagnose/main.go:99 +0x287
[2023-04-02T07:39:30.205487300Z][com.docker.diagnose.exe][I] (1afa7504) 855070d3-diagnose C->S diagnosticsd GET /ping
[2023-04-02T07:39:30.205487300Z][com.docker.diagnose.exe][W] (1afa7504) 855070d3-diagnose C<-S NoResponse GET /ping (0s): 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-02T07:39:30.206529600Z][com.docker.diagnose.exe][I] ipc.NewClient: 801d1e13-com.docker.diagnose -> \.\pipe\dockerLifecycleServer VMDockerdAPI
[linuxkit/pkg/desktop-host-tools/pkg/client.NewClientForPath(...)
[ linuxkit/pkg/desktop-host-tools/pkg/client/client.go:61
[linuxkit/pkg/desktop-host-tools/pkg/client.NewClient({0x16f68bf, 0x13})
[ linuxkit/pkg/desktop-host-tools/pkg/client/client.go:55 +0x99
[common/pkg/diagkit/gather/diagnose.isDockerEngineRunning()
[ common/pkg/diagkit/gather/diagnose/dockerd.go:21 +0x29
[common/pkg/diagkit/gather/diagnose.(*test).GetResult(0x1c94140)
[ common/pkg/diagkit/gather/diagnose/test.go:46 +0x43
[common/pkg/diagkit/gather/diagnose.Run.func1(0x1c94140)
[ common/pkg/diagkit/gather/diagnose/run.go:17 +0x5a
[common/pkg/diagkit/gather/diagnose.walkOnce.func1(0x3?, 0x1c94140)
[ common/pkg/diagkit/gather/diagnose/run.go:142 +0x77
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x2, 0x1c94140, 0xc00022f728)
[ common/pkg/diagkit/gather/diagnose/run.go:151 +0x87
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x1, 0x1c941c0, 0xc00022f728)
[ common/pkg/diagkit/gather/diagnose/run.go:148 +0x52
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x0, 0x1c94940, 0xc00022f728)
[ common/pkg/diagkit/gather/diagnose/run.go:148 +0x52
[common/pkg/diagkit/gather/diagnose.walkOnce(0x1632c80?, 0xc00035f890)
[ common/pkg/diagkit/gather/diagnose/run.go:137 +0xcc
[common/pkg/diagkit/gather/diagnose.Run(0x1c94940, 0x321e669500000010?, {0xc00035fb20, 0x1, 0x1})
[ common/pkg/diagkit/gather/diagnose/run.go:16 +0x1d4
[main.checkCmd({0xc0001163b0?, 0xc0001163b0?, 0x4?}, {0x0, 0x0})
[ common/cmd/com.docker.diagnose/main.go:133 +0x105
[main.main()
[ common/cmd/com.docker.diagnose/main.go:99 +0x287
[2023-04-02T07:39:30.207051400Z][com.docker.diagnose.exe][I] (471e8550) 801d1e13-com.docker.diagnose C->S VMDockerdAPI GET /docker
[2023-04-02T07:39:30.207573000Z][com.docker.diagnose.exe][W] (471e8550) 801d1e13-com.docker.diagnose C<-S NoResponse GET /docker (521.6µs): Get "http://ipc/docker": open \.\pipe\dockerLifecycleServer: The system cannot find the file specified.
[2023-04-02T07:39:30.208096500Z][com.docker.diagnose.exe][I] (471e8550-1) 801d1e13-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-04-02T07:39:30.208096500Z][com.docker.diagnose.exe][W] (471e8550-1) 801d1e13-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-02T07:39:31.221209900Z][com.docker.diagnose.exe][I] (471e8550-2) 801d1e13-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-04-02T07:39:31.221714100Z][com.docker.diagnose.exe][W] (471e8550-2) 801d1e13-com.docker.diagnose C<-S NoResponse GET /ping (504.2µs): Get "http://ipc/ping": open \.\pipe\dockerLifecycleServer: The system cannot find the file specified.
[2023-04-02T07:39:32.228354800Z][com.docker.diagnose.exe][I] (471e8550-3) 801d1e13-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-04-02T07:39:32.228354800Z][com.docker.diagnose.exe][W] (471e8550-3) 801d1e13-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-02T07:39:33.242757600Z][com.docker.diagnose.exe][I] (471e8550-4) 801d1e13-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-04-02T07:39:33.242757600Z][com.docker.diagnose.exe][W] (471e8550-4) 801d1e13-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-02T07:39:34.244385900Z][com.docker.diagnose.exe][I] (471e8550-5) 801d1e13-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-04-02T07:39:34.244466900Z][com.docker.diagnose.exe][W] (471e8550-5) 801d1e13-com.docker.diagnose C<-S NoResponse GET /ping (81µs): Get "http://ipc/ping": open \.\pipe\dockerLifecycleServer: The system cannot find the file specified.
[2023-04-02T07:39:35.257731800Z][com.docker.diagnose.exe][I] (471e8550-6) 801d1e13-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-04-02T07:39:35.257731800Z][com.docker.diagnose.exe][W] (471e8550-6) 801d1e13-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-02T07:39:36.271020400Z][com.docker.diagnose.exe][I] (471e8550-7) 801d1e13-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-04-02T07:39:36.271531700Z][com.docker.diagnose.exe][W] (471e8550-7) 801d1e13-com.docker.diagnose C<-S NoResponse GET /ping (511.3µs): Get "http://ipc/ping": open \.\pipe\dockerLifecycleServer: The system cannot find the file specified.
[2023-04-02T07:39:37.272654500Z][com.docker.diagnose.exe][I] (471e8550-8) 801d1e13-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-04-02T07:39:37.272654500Z][com.docker.diagnose.exe][W] (471e8550-8) 801d1e13-com.docker.diagnose C<-S NoResponse GET /ping (0s): 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: 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.
[PASS] DD0013: is the $PATH ok?
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
[FAIL] DD0005: is the user in the docker-users group? The user name could not be found.
[FAIL] DD0014: are the backend processes running? 4 errors occurred:
* com.docker.proxy.exe is not running
* com.docker.wsl-distro-proxy.exe is not running
* vpnkit-bridge.exe is not running
* com.docker.vpnkit.exe is not running
[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-02T07:39:41.310149700Z][com.docker.diagnose.exe][I] ipc.NewClient: dbbd364b-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(0x1c94640)
[ common/pkg/diagkit/gather/diagnose/test.go:46 +0x43
[common/pkg/diagkit/gather/diagnose.Run.func1(0x1c94640)
[ common/pkg/diagkit/gather/diagnose/run.go:17 +0x5a
[common/pkg/diagkit/gather/diagnose.walkOnce.func1(0x2?, 0x1c94640)
[ common/pkg/diagkit/gather/diagnose/run.go:142 +0x77
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x1, 0x1c94640, 0xc00023b728)
[ common/pkg/diagkit/gather/diagnose/run.go:151 +0x87
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x0, 0x1c94940, 0xc00023b728)
[ common/pkg/diagkit/gather/diagnose/run.go:148 +0x52
[common/pkg/diagkit/gather/diagnose.walkOnce(0x1632c80?, 0xc00035f890)
[ common/pkg/diagkit/gather/diagnose/run.go:137 +0xcc
[common/pkg/diagkit/gather/diagnose.Run(0x1c94940, 0x321e669500000010?, {0xc00035fb20, 0x1, 0x1})
[ common/pkg/diagkit/gather/diagnose/run.go:16 +0x1d4
[main.checkCmd({0xc0001163b0?, 0xc0001163b0?, 0x4?}, {0x0, 0x0})
[ common/cmd/com.docker.diagnose/main.go:133 +0x105
[main.main()
[ common/cmd/com.docker.diagnose/main.go:99 +0x287
[2023-04-02T07:39:41.310149700Z][com.docker.diagnose.exe][I] (0040d23c) dbbd364b-diagnose C->S Proxy GET /desktop-diagnostics/ping
[2023-04-02T07:39:41.310717600Z][com.docker.diagnose.exe][W] (0040d23c) dbbd364b-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-04-02T07:39:41.311248200Z][com.docker.diagnose.exe][I] (0040d23c-1) dbbd364b-diagnose C->S Proxy GET /ping
[2023-04-02T07:39:41.311312200Z][com.docker.diagnose.exe][W] (0040d23c-1) dbbd364b-diagnose C<-S NoResponse GET /ping (64µs): Get "http://ipc/ping": open \.\pipe\dockerDesktopLinuxEngine: The system cannot find the file specified.
[2023-04-02T07:39:42.323066600Z][com.docker.diagnose.exe][I] (0040d23c-2) dbbd364b-diagnose C->S Proxy GET /ping
[2023-04-02T07:39:42.323066600Z][com.docker.diagnose.exe][W] (0040d23c-2) dbbd364b-diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \.\pipe\dockerDesktopLinuxEngine: The system cannot find the file specified.
[2023-04-02T07:39:43.324194600Z][com.docker.diagnose.exe][I] (0040d23c-3) dbbd364b-diagnose C->S Proxy GET /ping
[2023-04-02T07:39:43.324194600Z][com.docker.diagnose.exe][W] (0040d23c-3) dbbd364b-diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \.\pipe\dockerDesktopLinuxEngine: The system cannot find the file specified.
[2023-04-02T07:39:44.337274000Z][com.docker.diagnose.exe][I] (0040d23c-4) dbbd364b-diagnose C->S Proxy GET /ping
[2023-04-02T07:39:44.337274000Z][com.docker.diagnose.exe][W] (0040d23c-4) dbbd364b-diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \.\pipe\dockerDesktopLinuxEngine: The system cannot find the file specified.
[2023-04-02T07:39:45.352112600Z][com.docker.diagnose.exe][I] (0040d23c-5) dbbd364b-diagnose C->S Proxy GET /ping
[2023-04-02T07:39:45.352112600Z][com.docker.diagnose.exe][W] (0040d23c-5) dbbd364b-diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \.\pipe\dockerDesktopLinuxEngine: The system cannot find the file specified.
[2023-04-02T07:39:46.352958900Z][com.docker.diagnose.exe][I] (0040d23c-6) dbbd364b-diagnose C->S Proxy GET /ping
[2023-04-02T07:39:46.353514200Z][com.docker.diagnose.exe][W] (0040d23c-6) dbbd364b-diagnose C<-S NoResponse GET /ping (555.3µs): Get "http://ipc/ping": open \.\pipe\dockerDesktopLinuxEngine: The system cannot find the file specified.
[2023-04-02T07:39:47.353657600Z][com.docker.diagnose.exe][I] (0040d23c-7) dbbd364b-diagnose C->S Proxy GET /ping
[2023-04-02T07:39:47.353657600Z][com.docker.diagnose.exe][W] (0040d23c-7) dbbd364b-diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \.\pipe\dockerDesktopLinuxEngine: The system cannot find the file specified.
[2023-04-02T07:39:48.368806900Z][com.docker.diagnose.exe][I] (0040d23c-8) dbbd364b-diagnose C->S Proxy GET /ping
[2023-04-02T07:39:48.368806900Z][com.docker.diagnose.exe][W] (0040d23c-8) dbbd364b-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-04-02T07:39:48.455336800Z][com.docker.diagnose.exe][I] ipc.NewClient: 5cac3ff2-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(0x1c94340)
[ common/pkg/diagkit/gather/diagnose/test.go:46 +0x43
[common/pkg/diagkit/gather/diagnose.Run.func1(0x1c94340)
[ common/pkg/diagkit/gather/diagnose/run.go:17 +0x5a
[common/pkg/diagkit/gather/diagnose.walkOnce.func1(0x2?, 0x1c94340)
[ common/pkg/diagkit/gather/diagnose/run.go:142 +0x77
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x1, 0x1c94340, 0xc00023b728)
[ common/pkg/diagkit/gather/diagnose/run.go:151 +0x87
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x0, 0x1c94940, 0xc00023b728)
[ common/pkg/diagkit/gather/diagnose/run.go:148 +0x52
[common/pkg/diagkit/gather/diagnose.walkOnce(0x1632c80?, 0xc00035f890)
[ common/pkg/diagkit/gather/diagnose/run.go:137 +0xcc
[common/pkg/diagkit/gather/diagnose.Run(0x1c94940, 0x321e669500000010?, {0xc00035fb20, 0x1, 0x1})
[ common/pkg/diagkit/gather/diagnose/run.go:16 +0x1d4
[main.checkCmd({0xc0001163b0?, 0xc0001163b0?, 0x4?}, {0x0, 0x0})
[ common/cmd/com.docker.diagnose/main.go:133 +0x105
[main.main()
[ common/cmd/com.docker.diagnose/main.go:99 +0x287
[2023-04-02T07:39:48.455839900Z][com.docker.diagnose.exe][I] (97baece1) 5cac3ff2-diagnose-network C->S diagnosticsd POST /check-network-connectivity: {"ips":["192.168.0.108","100.64.248.170","172.20.224.1","172.18.176.1"]}
[2023-04-02T07:39:48.455839900Z][com.docker.diagnose.exe][W] (97baece1) 5cac3ff2-diagnose-network C<-S NoResponse POST /check-network-connectivity (503.1µs): Post "http://ipc/check-network-connectivity": open \.\pipe\dockerDiagnosticd: The system cannot find the file specified.
[2023-04-02T07:39:48.456355200Z][com.docker.diagnose.exe][I] (97baece1-1) 5cac3ff2-diagnose-network C->S diagnosticsd GET /ping
[2023-04-02T07:39:48.456355200Z][com.docker.diagnose.exe][W] (97baece1-1) 5cac3ff2-diagnose-network C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \.\pipe\dockerDiagnosticd: The system cannot find the file specified.
[2023-04-02T07:39:49.459203800Z][com.docker.diagnose.exe][I] (97baece1-2) 5cac3ff2-diagnose-network C->S diagnosticsd GET /ping
[2023-04-02T07:39:49.459203800Z][com.docker.diagnose.exe][W] (97baece1-2) 5cac3ff2-diagnose-network C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \.\pipe\dockerDiagnosticd: The system cannot find the file specified.
[2023-04-02T07:39:50.468895800Z][com.docker.diagnose.exe][I] (97baece1-3) 5cac3ff2-diagnose-network C->S diagnosticsd GET /ping
[2023-04-02T07:39:50.468895800Z][com.docker.diagnose.exe][W] (97baece1-3) 5cac3ff2-diagnose-network C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \.\pipe\dockerDiagnosticd: The system cannot find the file specified.
[2023-04-02T07:39:51.481628400Z][com.docker.diagnose.exe][I] (97baece1-4) 5cac3ff2-diagnose-network C->S diagnosticsd GET /ping
[2023-04-02T07:39:51.481628400Z][com.docker.diagnose.exe][W] (97baece1-4) 5cac3ff2-diagnose-network C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \.\pipe\dockerDiagnosticd: The system cannot find the file specified.
[2023-04-02T07:39:52.493499200Z][com.docker.diagnose.exe][I] (97baece1-5) 5cac3ff2-diagnose-network C->S diagnosticsd GET /ping
[2023-04-02T07:39:52.493499200Z][com.docker.diagnose.exe][W] (97baece1-5) 5cac3ff2-diagnose-network C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \.\pipe\dockerDiagnosticd: The system cannot find the file specified.
[2023-04-02T07:39:53.508019400Z][com.docker.diagnose.exe][I] (97baece1-6) 5cac3ff2-diagnose-network C->S diagnosticsd GET /ping
[2023-04-02T07:39:53.508019400Z][com.docker.diagnose.exe][W] (97baece1-6) 5cac3ff2-diagnose-network C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \.\pipe\dockerDiagnosticd: The system cannot find the file specified.
[2023-04-02T07:39:54.517121400Z][com.docker.diagnose.exe][I] (97baece1-7) 5cac3ff2-diagnose-network C->S diagnosticsd GET /ping
[2023-04-02T07:39:54.517121400Z][com.docker.diagnose.exe][W] (97baece1-7) 5cac3ff2-diagnose-network C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \.\pipe\dockerDiagnosticd: The system cannot find the file specified.
[2023-04-02T07:39:55.528965900Z][com.docker.diagnose.exe][I] (97baece1-8) 5cac3ff2-diagnose-network C->S diagnosticsd GET /ping
[2023-04-02T07:39:55.528965900Z][com.docker.diagnose.exe][W] (97baece1-8) 5cac3ff2-diagnose-network C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \.\pipe\dockerDiagnosticd: The system cannot find the file specified.
[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?
[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?
[WARN] 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.
[WARN] 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.
Please note the following 4 warnings:
1 : The check: are the LinuxKit services running?
Produced the following warning: 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.
2 : The check: is the Docker engine running?
Produced the following warning: Get "http://ipc/docker": open \.\pipe\dockerLifecycleServer: The system cannot find the file specified.
The Docker engine manages all containers and images on the host. Check the dockerd.log to see why it failed to start.
3 : The check: does the Docker API work?
Produced the following warning: 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.
If the Docker API is not available from the host then Docker Desktop will not work correctly.
4 : The check: do Docker networks overlap with host IPs?
Produced the following warning: 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.
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 4 issues:
1 : The test: are the backend processes running?
Failed with: 4 errors occurred:
* com.docker.proxy.exe is not running
* com.docker.wsl-distro-proxy.exe is not running
* vpnkit-bridge.exe is not running
* com.docker.vpnkit.exe is not running
Not all of the backend processes are running.
Steps to reproduce the behavior
The text was updated successfully, but these errors were encountered: