<!--
************************************************************************…************
*READ ME FIRST*
This repository is for reporting bugs with the Docker Desktop for Windows software,
which we respond to on a best-effort basis.
Do *not* paste logfiles into github issues: upload diagnostics instead, which are
only visible to Docker engineers.
Support requests in this repository (i.e., trouble installing or using the
software) will be ignored, but personalized support is available to Docker Pro and
Team customers at https://hub.docker.com/support/desktop/, and community support is
available from the Docker community Slack (https://www.docker.com/docker-community).
Issues without sufficient detail to debug them will be closed. They generally need
a clear title and description, steps to reproduce, and a diagnostics ID. See
https://docs.docker.com/docker-for-windows/troubleshoot/#diagnose-and-feedback for
how to generate a diagnostics ID either from inside the app or from the command line.
************************************************************************************
-->
- [x] I have tried with the latest version of Docker Desktop
- [x] I have tried disabling enabled experimental features
- [ ] I have uploaded Diagnostics
- Diagnostics ID:
### Background
WSL2 is configured correctly. The computer is brand new so storage/resources are not the problems. Following the wsl installation guide, Virtual Machine Platform and Windows Subsystem for Linux have been selected in windows features. Below are the results of wsl version info pre docker installation
> wsl -l -v
| Name | State | Version |
|--------|---------|---------|
| Ubuntu | Running | 2 |
Two days ago, docker daemon was able to start and containers were able to be built
### Actual behavior
Docker daemon no longer starts. I've restarted docker desktop, I've restarted the computer, I've purged data, I've factory reset, I've uninstalled and reinstalled Docker Desktop over 6 times, I've installed through the command line and I've installed older Docker Desktop versions. Nothing has help with the issue. The first 5 times I installed Docker Desktop the daemon would fail and display the "Docker Desktop failed to start..." with no additional info. Now the Docker Desktop is just getting hung at "Docker Desktop is starting...", never makes it any further (see the sreenshots below).
Original Issue
![image](https://user-images.githubusercontent.com/81196676/196516241-b5252994-bc81-4870-8f2c-c9770a72c2b0.png)
Fresh New Take
![image](https://user-images.githubusercontent.com/81196676/196515265-3e872cce-fa80-4334-bba2-14ed4c3d8bba.png)
Below are the results of wsl version info post docker failed installation
> wsl -l -v
![image](https://user-images.githubusercontent.com/81196676/196514867-c593ba5f-392e-4c37-b749-68164a51e82e.png)
### Expected behavior
A running Docker Daemon with Docker Desktop
### Information
<!--
Please, help us understand the problem. For instance:
- Is it reproducible?
- Is the problem new?
- Did the problem appear with an update?
- A reproducible case if this is a bug, Dockerfiles with reproduction inside is best.
-->
- Windows Version: Windows 11 Home
- Docker Desktop Version: 4.12.0
- WSL2 or Hyper-V backend? WSL
- Are you running inside a virtualized Windows e.g. on a cloud server or a VM: No, Trying to run with WSL2
### Output of `& "C:\Program Files\Docker\Docker\resources\com.docker.diagnose.exe" check`
Starting diagnostics
[PASS] DD0027: is there available disk space on the host?
[SKIP] DD0028: is there available VM disk space?
[FAIL] DD0031: does the Docker API work? error during connect: In the default daemon configuration on Windows, the docker client must be run with elevated privileges to connect.: Get "http://%2F%2F.%2Fpipe%2Fdocker_engine_linux/v1.24/containers/json?limit=0": open //./pipe/docker_engine_linux: The system cannot find the file specified.
[FAIL] DD0004: is the Docker engine running? Get "http://ipc/docker": open \\.\pipe\dockerLifecycleServer: The system cannot find the file specified.
[2022-10-18T18:17:26.525068700Z][com.docker.diagnose.exe][I] ipc.NewClient: f770b079-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({0xbb655d, 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(0x11630a0)
[ common/pkg/diagkit/gather/diagnose/test.go:46 +0x43
[common/pkg/diagkit/gather/diagnose.Run.func1(0x11630a0)
[ common/pkg/diagkit/gather/diagnose/run.go:17 +0x5a
[common/pkg/diagkit/gather/diagnose.walkOnce.func1(0xa0cb77?, 0x11630a0)
[ common/pkg/diagkit/gather/diagnose/run.go:140 +0x77
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x2, 0x11630a0, 0xc00035f728)
[ common/pkg/diagkit/gather/diagnose/run.go:146 +0x36
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x1, 0x1163120?, 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(0xaf2340?, 0xc00035f890)
[ common/pkg/diagkit/gather/diagnose/run.go:135 +0xcc
[common/pkg/diagkit/gather/diagnose.Run(0x11638a0, 0xa331383b00000010?, {0xc00035fb20, 0x1, 0x1})
[ common/pkg/diagkit/gather/diagnose/run.go:16 +0x1d4
[main.checkCmd({0xc0001923b0?, 0xc0001923b0?, 0x4?}, {0x0, 0x0})
[ common/cmd/com.docker.diagnose/main.go:133 +0x105
[main.main()
[ common/cmd/com.docker.diagnose/main.go:99 +0x287
[2022-10-18T18:17:26.527074100Z][com.docker.diagnose.exe][I] (ef48dffa) f770b079-com.docker.diagnose C->S VMDockerdAPI GET /docker
[2022-10-18T18:17:26.527074100Z][com.docker.diagnose.exe][W] (ef48dffa) f770b079-com.docker.diagnose C<-S NoResponse GET /docker (0s): Get "http://ipc/docker": open \\.\pipe\dockerLifecycleServer: The system cannot find the file specified.
[2022-10-18T18:17:26.527074100Z][com.docker.diagnose.exe][I] (ef48dffa-1) f770b079-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2022-10-18T18:17:26.527074100Z][com.docker.diagnose.exe][W] (ef48dffa-1) f770b079-com.docker.diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \\.\pipe\dockerLifecycleServer: The system cannot find the file specified.
[2022-10-18T18:17:27.547820600Z][com.docker.diagnose.exe][I] (ef48dffa-2) f770b079-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2022-10-18T18:17:27.548827500Z][com.docker.diagnose.exe][W] (ef48dffa-2) f770b079-com.docker.diagnose C<-S NoResponse GET /ping (1.0069ms): Get "http://ipc/ping": open \\.\pipe\dockerLifecycleServer: The system cannot find the file specified.
[2022-10-18T18:17:28.549294000Z][com.docker.diagnose.exe][I] (ef48dffa-3) f770b079-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2022-10-18T18:17:28.550294100Z][com.docker.diagnose.exe][W] (ef48dffa-3) f770b079-com.docker.diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \\.\pipe\dockerLifecycleServer: The system cannot find the file specified.
[2022-10-18T18:17:29.554547200Z][com.docker.diagnose.exe][I] (ef48dffa-4) f770b079-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2022-10-18T18:17:29.555614200Z][com.docker.diagnose.exe][W] (ef48dffa-4) f770b079-com.docker.diagnose C<-S NoResponse GET /ping (1.067ms): Get "http://ipc/ping": open \\.\pipe\dockerLifecycleServer: The system cannot find the file specified.
[2022-10-18T18:17:30.561961600Z][com.docker.diagnose.exe][I] (ef48dffa-5) f770b079-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2022-10-18T18:17:30.563009900Z][com.docker.diagnose.exe][W] (ef48dffa-5) f770b079-com.docker.diagnose C<-S NoResponse GET /ping (1.0483ms): Get "http://ipc/ping": open \\.\pipe\dockerLifecycleServer: The system cannot find the file specified.
[2022-10-18T18:17:31.570465900Z][com.docker.diagnose.exe][I] (ef48dffa-6) f770b079-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2022-10-18T18:17:31.571360600Z][com.docker.diagnose.exe][W] (ef48dffa-6) f770b079-com.docker.diagnose C<-S NoResponse GET /ping (894.7┬╡s): Get "http://ipc/ping": open \\.\pipe\dockerLifecycleServer: The system cannot find the file specified.
[2022-10-18T18:17:32.576058800Z][com.docker.diagnose.exe][I] (ef48dffa-7) f770b079-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2022-10-18T18:17:32.577461100Z][com.docker.diagnose.exe][W] (ef48dffa-7) f770b079-com.docker.diagnose C<-S NoResponse GET /ping (1.4023ms): Get "http://ipc/ping": open \\.\pipe\dockerLifecycleServer: The system cannot find the file specified.
[2022-10-18T18:17:33.590671500Z][com.docker.diagnose.exe][I] (ef48dffa-8) f770b079-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2022-10-18T18:17:33.591671200Z][com.docker.diagnose.exe][W] (ef48dffa-8) f770b079-com.docker.diagnose C<-S NoResponse GET /ping (999.7┬╡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.
[2022-10-18T18:17:33.591671200Z][com.docker.diagnose.exe][I] ipc.NewClient: bccbbaa6-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(0x1163020)
[ common/pkg/diagkit/gather/diagnose/test.go:46 +0x43
[common/pkg/diagkit/gather/diagnose.Run.func1(0x1163020)
[ common/pkg/diagkit/gather/diagnose/run.go:17 +0x5a
[common/pkg/diagkit/gather/diagnose.walkOnce.func1(0xa0cb77?, 0x1163020)
[ common/pkg/diagkit/gather/diagnose/run.go:140 +0x77
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x3, 0x1163020, 0xc00069f728)
[ common/pkg/diagkit/gather/diagnose/run.go:146 +0x36
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x2, 0x11630a0?, 0xc00069f728)
[ common/pkg/diagkit/gather/diagnose/run.go:149 +0x73
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x1, 0x1163120?, 0xc00069f728)
[ common/pkg/diagkit/gather/diagnose/run.go:149 +0x73
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x0, 0xcb?, 0xc00069f728)
[ common/pkg/diagkit/gather/diagnose/run.go:149 +0x73
[common/pkg/diagkit/gather/diagnose.walkOnce(0xaf2340?, 0xc00035f890)
[ common/pkg/diagkit/gather/diagnose/run.go:135 +0xcc
[common/pkg/diagkit/gather/diagnose.Run(0x11638a0, 0xa331383b00000010?, {0xc00035fb20, 0x1, 0x1})
[ common/pkg/diagkit/gather/diagnose/run.go:16 +0x1d4
[main.checkCmd({0xc0001923b0?, 0xc0001923b0?, 0x4?}, {0x0, 0x0})
[ common/cmd/com.docker.diagnose/main.go:133 +0x105
[main.main()
[ common/cmd/com.docker.diagnose/main.go:99 +0x287
[2022-10-18T18:17:33.591671200Z][com.docker.diagnose.exe][I] (9c85ad7f) bccbbaa6-diagnose C->S diagnosticsd GET /ping
[2022-10-18T18:17:33.601868900Z][com.docker.diagnose.exe][W] (9c85ad7f) bccbbaa6-diagnose C<-S NoResponse GET /ping (10.1977ms): 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?
[FAIL] DD0023: is the Containers Windows Feature enabled? required Windows Feature not installed: Containers
[2022-10-18T18:17:35.216811800Z][com.docker.diagnose.exe][I] ipc.NewClient: 3f388aa4-com.docker.diagnose -> \\.\pipe\dockerBackendV2 com.docker.service.exe
[common/pkg/windows/serviceclient.NewClientForPath(...)
[ common/pkg/windows/serviceclient/service.go:44
[common/pkg/windows/serviceclient.NewClient({0xbb655d, 0x13}, {0x0, 0x0, 0x0})
[ common/pkg/windows/serviceclient/service.go:33 +0xc5
[common/pkg/diagkit/gather/diagnose.checkWindowsFeature({{0xbae565?, 0x1156670?}, {0xbae565?, 0x1?}})
[ common/pkg/diagkit/gather/diagnose/features_windows.go:11 +0x51
[common/pkg/diagkit/gather/diagnose.glob..func6()
[ common/pkg/diagkit/gather/diagnose/dockerd_windows.go:11 +0x35
[common/pkg/diagkit/gather/diagnose.(*test).GetResult(0x1163220)
[ common/pkg/diagkit/gather/diagnose/test.go:46 +0x43
[common/pkg/diagkit/gather/diagnose.Run.func1(0x1163220)
[ common/pkg/diagkit/gather/diagnose/run.go:17 +0x5a
[common/pkg/diagkit/gather/diagnose.walkOnce.func1(0x4?, 0x1163220)
[ common/pkg/diagkit/gather/diagnose/run.go:140 +0x77
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x3, 0x1163220, 0xc000535728)
[ common/pkg/diagkit/gather/diagnose/run.go:146 +0x36
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x2, 0x11630a0?, 0xc000535728)
[ common/pkg/diagkit/gather/diagnose/run.go:149 +0x73
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x1, 0x1163120?, 0xc000535728)
[ common/pkg/diagkit/gather/diagnose/run.go:149 +0x73
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x0, 0xcb?, 0xc000535728)
[ common/pkg/diagkit/gather/diagnose/run.go:149 +0x73
[common/pkg/diagkit/gather/diagnose.walkOnce(0xaf2340?, 0xc00035f890)
[ common/pkg/diagkit/gather/diagnose/run.go:135 +0xcc
[common/pkg/diagkit/gather/diagnose.Run(0x11638a0, 0xa331383b00000010?, {0xc00035fb20, 0x1, 0x1})
[ common/pkg/diagkit/gather/diagnose/run.go:16 +0x1d4
[main.checkCmd({0xc0001923b0?, 0xc0001923b0?, 0x4?}, {0x0, 0x0})
[ common/cmd/com.docker.diagnose/main.go:133 +0x105
[main.main()
[ common/cmd/com.docker.diagnose/main.go:99 +0x287
[2022-10-18T18:17:35.217316800Z][com.docker.diagnose.exe][I] (57c92fbe) 3f388aa4-com.docker.diagnose C->S com.docker.service.exe POST /windowsfeatures/check: [{Name:Containers Description:Containers}]
[2022-10-18T18:17:35.815527500Z][com.docker.diagnose.exe][I] (57c92fbe) 3f388aa4-com.docker.diagnose C<-S e0b9e3ba-ServiceAPI POST /windowsfeatures/check (597.6937ms): {"NotAvailable":[{"Description":"Containers","Name":"Containers"}],"NotEnabled":[]}
[PASS] DD0015: are the binary symlinks installed?
[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? 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
* vpnkit.exe is not running
[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\dockerDesktopWindowsEngine: The system cannot find the file specified.
[2022-10-18T18:17:37.751520000Z][com.docker.diagnose.exe][I] ipc.NewClient: cab15065-diagnose -> \\.\pipe\dockerDesktopWindowsEngine Proxy
[common/pkg/diagkit/gather/diagnose.glob..func12()
[ common/pkg/diagkit/gather/diagnose/ipc.go:91 +0x7a
[common/pkg/diagkit/gather/diagnose.(*test).GetResult(0x11635a0)
[ common/pkg/diagkit/gather/diagnose/test.go:46 +0x43
[common/pkg/diagkit/gather/diagnose.Run.func1(0x11635a0)
[ common/pkg/diagkit/gather/diagnose/run.go:17 +0x5a
[common/pkg/diagkit/gather/diagnose.walkOnce.func1(0x2?, 0x11635a0)
[ common/pkg/diagkit/gather/diagnose/run.go:140 +0x77
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x1, 0x11635a0, 0xc0001c3728)
[ common/pkg/diagkit/gather/diagnose/run.go:146 +0x36
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x0, 0xcb?, 0xc0001c3728)
[ common/pkg/diagkit/gather/diagnose/run.go:149 +0x73
[common/pkg/diagkit/gather/diagnose.walkOnce(0xaf2340?, 0xc00035f890)
[ common/pkg/diagkit/gather/diagnose/run.go:135 +0xcc
[common/pkg/diagkit/gather/diagnose.Run(0x11638a0, 0xa331383b00000010?, {0xc00035fb20, 0x1, 0x1})
[ common/pkg/diagkit/gather/diagnose/run.go:16 +0x1d4
[main.checkCmd({0xc0001923b0?, 0xc0001923b0?, 0x4?}, {0x0, 0x0})
[ common/cmd/com.docker.diagnose/main.go:133 +0x105
[main.main()
[ common/cmd/com.docker.diagnose/main.go:99 +0x287
[2022-10-18T18:17:37.752050800Z][com.docker.diagnose.exe][I] (6315636e) cab15065-diagnose C->S Proxy GET /desktop-diagnostics/ping
[2022-10-18T18:17:37.752050800Z][com.docker.diagnose.exe][W] (6315636e) cab15065-diagnose C<-S NoResponse GET /desktop-diagnostics/ping (0s): Get "http://ipc/desktop-diagnostics/ping": open \\.\pipe\dockerDesktopWindowsEngine: The system cannot find the file specified.
[2022-10-18T18:17:37.752050800Z][com.docker.diagnose.exe][I] (6315636e-1) cab15065-diagnose C->S Proxy GET /ping
[2022-10-18T18:17:37.752599600Z][com.docker.diagnose.exe][W] (6315636e-1) cab15065-diagnose C<-S NoResponse GET /ping (548.8┬╡s): Get "http://ipc/ping": open \\.\pipe\dockerDesktopWindowsEngine: The system cannot find the file specified.
[2022-10-18T18:17:38.753287000Z][com.docker.diagnose.exe][I] (6315636e-2) cab15065-diagnose C->S Proxy GET /ping
[2022-10-18T18:17:38.763199700Z][com.docker.diagnose.exe][W] (6315636e-2) cab15065-diagnose C<-S NoResponse GET /ping (9.9127ms): Get "http://ipc/ping": open \\.\pipe\dockerDesktopWindowsEngine: The system cannot find the file specified.
[2022-10-18T18:17:39.777551600Z][com.docker.diagnose.exe][I] (6315636e-3) cab15065-diagnose C->S Proxy GET /ping
[2022-10-18T18:17:39.778056700Z][com.docker.diagnose.exe][W] (6315636e-3) cab15065-diagnose C<-S NoResponse GET /ping (505.1┬╡s): Get "http://ipc/ping": open \\.\pipe\dockerDesktopWindowsEngine: The system cannot find the file specified.
[2022-10-18T18:17:40.787111700Z][com.docker.diagnose.exe][I] (6315636e-4) cab15065-diagnose C->S Proxy GET /ping
[2022-10-18T18:17:40.787489700Z][com.docker.diagnose.exe][W] (6315636e-4) cab15065-diagnose C<-S NoResponse GET /ping (378┬╡s): Get "http://ipc/ping": open \\.\pipe\dockerDesktopWindowsEngine: The system cannot find the file specified.
[2022-10-18T18:17:41.796662000Z][com.docker.diagnose.exe][I] (6315636e-5) cab15065-diagnose C->S Proxy GET /ping
[2022-10-18T18:17:41.797267100Z][com.docker.diagnose.exe][W] (6315636e-5) cab15065-diagnose C<-S NoResponse GET /ping (605.1┬╡s): Get "http://ipc/ping": open \\.\pipe\dockerDesktopWindowsEngine: The system cannot find the file specified.
[2022-10-18T18:17:42.807240700Z][com.docker.diagnose.exe][I] (6315636e-6) cab15065-diagnose C->S Proxy GET /ping
[2022-10-18T18:17:42.807751800Z][com.docker.diagnose.exe][W] (6315636e-6) cab15065-diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \\.\pipe\dockerDesktopWindowsEngine: The system cannot find the file specified.
[2022-10-18T18:17:43.808563700Z][com.docker.diagnose.exe][I] (6315636e-7) cab15065-diagnose C->S Proxy GET /ping
[2022-10-18T18:17:43.809294600Z][com.docker.diagnose.exe][W] (6315636e-7) cab15065-diagnose C<-S NoResponse GET /ping (730.9┬╡s): Get "http://ipc/ping": open \\.\pipe\dockerDesktopWindowsEngine: The system cannot find the file specified.
[2022-10-18T18:17:44.813302400Z][com.docker.diagnose.exe][I] (6315636e-8) cab15065-diagnose C->S Proxy GET /ping
[2022-10-18T18:17:44.813829300Z][com.docker.diagnose.exe][W] (6315636e-8) cab15065-diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \\.\pipe\dockerDesktopWindowsEngine: 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.
[2022-10-18T18:17:45.000278100Z][com.docker.diagnose.exe][I] ipc.NewClient: 9448b433-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(0x11632a0)
[ common/pkg/diagkit/gather/diagnose/test.go:46 +0x43
[common/pkg/diagkit/gather/diagnose.Run.func1(0x11632a0)
[ common/pkg/diagkit/gather/diagnose/run.go:17 +0x5a
[common/pkg/diagkit/gather/diagnose.walkOnce.func1(0x2?, 0x11632a0)
[ common/pkg/diagkit/gather/diagnose/run.go:140 +0x77
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x1, 0x11632a0, 0xc0000ab728)
[ common/pkg/diagkit/gather/diagnose/run.go:146 +0x36
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x0, 0xcb?, 0xc0000ab728)
[ common/pkg/diagkit/gather/diagnose/run.go:149 +0x73
[common/pkg/diagkit/gather/diagnose.walkOnce(0xaf2340?, 0xc00035f890)
[ common/pkg/diagkit/gather/diagnose/run.go:135 +0xcc
[common/pkg/diagkit/gather/diagnose.Run(0x11638a0, 0xa331383b00000010?, {0xc00035fb20, 0x1, 0x1})
[ common/pkg/diagkit/gather/diagnose/run.go:16 +0x1d4
[main.checkCmd({0xc0001923b0?, 0xc0001923b0?, 0x4?}, {0x0, 0x0})
[ common/cmd/com.docker.diagnose/main.go:133 +0x105
[main.main()
[ common/cmd/com.docker.diagnose/main.go:99 +0x287
[2022-10-18T18:17:45.000907200Z][com.docker.diagnose.exe][I] (4db6cb8e) 9448b433-diagnose-network C->S diagnosticsd POST /check-network-connectivity: {"ips":["172.27.232.92","10.0.0.59","172.17.96.1"]}
[2022-10-18T18:17:45.001007200Z][com.docker.diagnose.exe][W] (4db6cb8e) 9448b433-diagnose-network C<-S NoResponse POST /check-network-connectivity (729.1┬╡s): Post "http://ipc/check-network-connectivity": open \\.\pipe\dockerDiagnosticd: The system cannot find the file specified.
[2022-10-18T18:17:45.001007200Z][com.docker.diagnose.exe][I] (4db6cb8e-1) 9448b433-diagnose-network C->S diagnosticsd GET /ping
[2022-10-18T18:17:45.001643700Z][com.docker.diagnose.exe][W] (4db6cb8e-1) 9448b433-diagnose-network C<-S NoResponse GET /ping (636.5┬╡s): Get "http://ipc/ping": open \\.\pipe\dockerDiagnosticd: The system cannot find the file specified.
[2022-10-18T18:17:46.008466600Z][com.docker.diagnose.exe][I] (4db6cb8e-2) 9448b433-diagnose-network C->S diagnosticsd GET /ping
[2022-10-18T18:17:46.009270800Z][com.docker.diagnose.exe][W] (4db6cb8e-2) 9448b433-diagnose-network C<-S NoResponse GET /ping (542.4┬╡s): Get "http://ipc/ping": open \\.\pipe\dockerDiagnosticd: The system cannot find the file specified.
[2022-10-18T18:17:47.022444600Z][com.docker.diagnose.exe][I] (4db6cb8e-3) 9448b433-diagnose-network C->S diagnosticsd GET /ping
[2022-10-18T18:17:47.022966400Z][com.docker.diagnose.exe][W] (4db6cb8e-3) 9448b433-diagnose-network C<-S NoResponse GET /ping (521.8┬╡s): Get "http://ipc/ping": open \\.\pipe\dockerDiagnosticd: The system cannot find the file specified.
[2022-10-18T18:17:48.028811000Z][com.docker.diagnose.exe][I] (4db6cb8e-4) 9448b433-diagnose-network C->S diagnosticsd GET /ping
[2022-10-18T18:17:48.029319500Z][com.docker.diagnose.exe][W] (4db6cb8e-4) 9448b433-diagnose-network C<-S NoResponse GET /ping (508.5┬╡s): Get "http://ipc/ping": open \\.\pipe\dockerDiagnosticd: The system cannot find the file specified.
[2022-10-18T18:17:49.030872500Z][com.docker.diagnose.exe][I] (4db6cb8e-5) 9448b433-diagnose-network C->S diagnosticsd GET /ping
[2022-10-18T18:17:49.032445500Z][com.docker.diagnose.exe][W] (4db6cb8e-5) 9448b433-diagnose-network C<-S NoResponse GET /ping (1.573ms): Get "http://ipc/ping": open \\.\pipe\dockerDiagnosticd: The system cannot find the file specified.
[2022-10-18T18:17:50.040255800Z][com.docker.diagnose.exe][I] (4db6cb8e-6) 9448b433-diagnose-network C->S diagnosticsd GET /ping
[2022-10-18T18:17:50.040767000Z][com.docker.diagnose.exe][W] (4db6cb8e-6) 9448b433-diagnose-network C<-S NoResponse GET /ping (511.2┬╡s): Get "http://ipc/ping": open \\.\pipe\dockerDiagnosticd: The system cannot find the file specified.
[2022-10-18T18:17:51.047406200Z][com.docker.diagnose.exe][I] (4db6cb8e-7) 9448b433-diagnose-network C->S diagnosticsd GET /ping
[2022-10-18T18:17:51.050891000Z][com.docker.diagnose.exe][W] (4db6cb8e-7) 9448b433-diagnose-network C<-S NoResponse GET /ping (3.4848ms): Get "http://ipc/ping": open \\.\pipe\dockerDiagnosticd: The system cannot find the file specified.
[2022-10-18T18:17:52.054312100Z][com.docker.diagnose.exe][I] (4db6cb8e-8) 9448b433-diagnose-network C->S diagnosticsd GET /ping
[2022-10-18T18:17:52.055333000Z][com.docker.diagnose.exe][W] (4db6cb8e-8) 9448b433-diagnose-network C<-S NoResponse GET /ping (1.0209ms): 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: In the default daemon configuration on Windows, the docker client must be run with elevated privileges to connect.: Get "http://%2F%2F.%2Fpipe%2Fdocker_engine_linux/v1.24/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: is the Containers Windows Feature enabled?
Failed with: required Windows Feature not installed: Containers
The Containers Windows Feature is needed to use Windows OSes inside containers.
2 : 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.
3 : 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
* vpnkit.exe is not running
Not all of the backend processes are running.
4 : 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.
-----------------------------------------------------------------
Ubuntu and wsl2 are currently running, Containers feature can't be found and every "http://ipc/ *" link fails
### Steps to reproduce the behavior
<!--
A reproducible case, Dockerfiles with reproduction inside is best.
-->
Can't even get to a point where Dockerfiles are relevant
1. Install wsl2 with Microsoft guidelines
2. Install Ubuntu
3. Set Ubuntu as default distro and confirm Version 2
4. Install Docker Desktop
5. Cry