<!--
************************************************************************…************
*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
- [x] I have uploaded Diagnostics
- Diagnostics ID:
### Actual behavior
While i'm building a mirror with following Dockerfile, I received a windows notification which tells me WSL2 backend has stopped unexpectedly. Also all other WSL2 VMs had shutdown.
![image](https://user-images.githubusercontent.com/30155715/175765415-d3e1da7b-b76e-4133-ab03-bbf345f3ff3f.png)
Docker console output is:
![image](https://user-images.githubusercontent.com/30155715/175765435-893c6918-9672-44b7-97ba-c84f2734af35.png)
Dockerfile:
```Dockerfile
FROM alpine as build-env
COPY . /opt/redos
RUN rm -rf /opt/redos/node.exe && rm -rf /opt/redos/Dockerfile
FROM node:latest
COPY --from=build-env /opt/redos /opt/redos
CMD ["node", "/opt/redos/bin/www"]
```
Basically `build-env` just delete windows version of node.js and Dockerfile from current directory. And I have a node.js project on current directory.
Sometimes this problem can be fixed by restarting WSL2 backend. But sometimes it will occur, not always.
Version of Docker Desktop: 4.8.1(78998)
WSL2 Backend
Windows 10 21H1
![image](https://user-images.githubusercontent.com/30155715/175765826-de5b6b2d-92d9-4aaa-a1b6-248afe3db218.png)
### Expected behavior
Build from dockerfile without problem.
### 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:
- 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`
This is right after the problem occured
```cmd
PS C:\Program Files\Docker\Docker\resources> .\com.docker.diagnose.exe check
Starting diagnostics
[PASS] DD0027: is there available disk space on the host?
[PASS] DD0028: is there available VM disk space?
[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.
[2022-06-25T08:41:21.649720200Z][com.docker.diagnose.exe][I] ipc.NewClient: fc7cb198-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({0x1149f20, 0x13})
[ linuxkit/pkg/desktop-host-tools/pkg/client/client.go:53 +0xa5
[common/pkg/diagkit/gather/diagnose.isDockerEngineRunning()
[ common/pkg/diagkit/gather/diagnose/dockerd.go:21 +0x29
[common/pkg/diagkit/gather/diagnose.(*test).GetResult(0x16bf6a0)
[ common/pkg/diagkit/gather/diagnose/test.go:46 +0x43
[common/pkg/diagkit/gather/diagnose.Run.func1(0x16bf6a0)
[ common/pkg/diagkit/gather/diagnose/run.go:17 +0x5a
[common/pkg/diagkit/gather/diagnose.walkOnce.func1(0xfaeab7?, 0x16bf6a0)
[ common/pkg/diagkit/gather/diagnose/run.go:140 +0x77
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x2, 0x16bf6a0, 0xc0002df730)
[ common/pkg/diagkit/gather/diagnose/run.go:146 +0x36
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x1, 0x16bf720?, 0xc0002df730)
[ common/pkg/diagkit/gather/diagnose/run.go:149 +0x73
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x0, 0xcb00000012?, 0xc0002df730)
[ common/pkg/diagkit/gather/diagnose/run.go:149 +0x73
[common/pkg/diagkit/gather/diagnose.walkOnce(0x108a960?, 0xc0002df890)
[ common/pkg/diagkit/gather/diagnose/run.go:135 +0xcc
[common/pkg/diagkit/gather/diagnose.Run(0x16bfea0, 0x1084300?, {0xc0002dfb20, 0x1, 0x1})
[ common/pkg/diagkit/gather/diagnose/run.go:16 +0x1cb
[main.checkCmd({0xc0000963b0?, 0xc0000963b0?, 0x4?}, {0x0, 0x0})
[ common/cmd/com.docker.diagnose/main.go:132 +0x105
[main.main()
[ common/cmd/com.docker.diagnose/main.go:98 +0x27f
[2022-06-25T08:41:21.649720200Z][com.docker.diagnose.exe][I] (1aeeddb1) fc7cb198-com.docker.diagnose C->S VMDockerdAPI GET /docker
[2022-06-25T08:41:21.651219100Z][com.docker.diagnose.exe][W] (1aeeddb1) fc7cb198-com.docker.diagnose C<-S NoResponse GET /docker (998.5µs): Get "http://ipc/docker": open \\.\pipe\dockerLifecycleServer: The system cannot find the file specified.
[2022-06-25T08:41:21.651219100Z][com.docker.diagnose.exe][I] (1aeeddb1-1) fc7cb198-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2022-06-25T08:41:21.651720000Z][com.docker.diagnose.exe][W] (1aeeddb1-1) fc7cb198-com.docker.diagnose C<-S NoResponse GET /ping (500.9µs): Get "http://ipc/ping": open \\.\pipe\dockerLifecycleServer: The system cannot find the file specified.
[2022-06-25T08:41:22.652200800Z][com.docker.diagnose.exe][I] (1aeeddb1-2) fc7cb198-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2022-06-25T08:41:22.652312100Z][com.docker.diagnose.exe][W] (1aeeddb1-2) fc7cb198-com.docker.diagnose C<-S NoResponse GET /ping (111.3µs): Get "http://ipc/ping": open \\.\pipe\dockerLifecycleServer: The system cannot find the file specified.
[2022-06-25T08:41:23.667359200Z][com.docker.diagnose.exe][I] (1aeeddb1-3) fc7cb198-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2022-06-25T08:41:23.667865700Z][com.docker.diagnose.exe][W] (1aeeddb1-3) fc7cb198-com.docker.diagnose C<-S NoResponse GET /ping (176.6µs): Get "http://ipc/ping": open \\.\pipe\dockerLifecycleServer: The system cannot find the file specified.
[2022-06-25T08:41:24.672386100Z][com.docker.diagnose.exe][I] (1aeeddb1-4) fc7cb198-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2022-06-25T08:41:24.672484900Z][com.docker.diagnose.exe][W] (1aeeddb1-4) fc7cb198-com.docker.diagnose C<-S NoResponse GET /ping (98.8µs): Get "http://ipc/ping": open \\.\pipe\dockerLifecycleServer: The system cannot find the file specified.
[2022-06-25T08:41:25.675460700Z][com.docker.diagnose.exe][I] (1aeeddb1-5) fc7cb198-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2022-06-25T08:41:25.675726200Z][com.docker.diagnose.exe][W] (1aeeddb1-5) fc7cb198-com.docker.diagnose C<-S NoResponse GET /ping (265.5µs): Get "http://ipc/ping": open \\.\pipe\dockerLifecycleServer: The system cannot find the file specified.
[2022-06-25T08:41:26.677639400Z][com.docker.diagnose.exe][I] (1aeeddb1-6) fc7cb198-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2022-06-25T08:41:26.677639400Z][com.docker.diagnose.exe][W] (1aeeddb1-6) fc7cb198-com.docker.diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \\.\pipe\dockerLifecycleServer: The system cannot find the file specified.
[2022-06-25T08:41:27.678507200Z][com.docker.diagnose.exe][I] (1aeeddb1-7) fc7cb198-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2022-06-25T08:41:27.678759400Z][com.docker.diagnose.exe][W] (1aeeddb1-7) fc7cb198-com.docker.diagnose C<-S NoResponse GET /ping (252.2µs): Get "http://ipc/ping": open \\.\pipe\dockerLifecycleServer: The system cannot find the file specified.
[2022-06-25T08:41:28.685341200Z][com.docker.diagnose.exe][I] (1aeeddb1-8) fc7cb198-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2022-06-25T08:41:28.685341200Z][com.docker.diagnose.exe][W] (1aeeddb1-8) fc7cb198-com.docker.diagnose C<-S NoResponse GET /ping (0s): 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-06-25T08:41:28.687231000Z][com.docker.diagnose.exe][I] ipc.NewClient: 8a63a04d-diagnose -> \\.\pipe\dockerDiagnosticd diagnosticsd
[common/pkg/diagkit/gather/diagnose.glob..func14()
[ common/pkg/diagkit/gather/diagnose/linuxkit.go:18 +0x92
[common/pkg/diagkit/gather/diagnose.(*test).GetResult(0x16bf620)
[ common/pkg/diagkit/gather/diagnose/test.go:46 +0x43
[common/pkg/diagkit/gather/diagnose.Run.func1(0x16bf620)
[ common/pkg/diagkit/gather/diagnose/run.go:17 +0x5a
[common/pkg/diagkit/gather/diagnose.walkOnce.func1(0xfaeab7?, 0x16bf620)
[ common/pkg/diagkit/gather/diagnose/run.go:140 +0x77
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x3, 0x16bf620, 0xc00069f730)
[ common/pkg/diagkit/gather/diagnose/run.go:146 +0x36
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x2, 0x16bf6a0?, 0xc00069f730)
[ common/pkg/diagkit/gather/diagnose/run.go:149 +0x73
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x1, 0x16bf720?, 0xc00069f730)
[ common/pkg/diagkit/gather/diagnose/run.go:149 +0x73
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x0, 0xcb00000012?, 0xc00069f730)
[ common/pkg/diagkit/gather/diagnose/run.go:149 +0x73
[common/pkg/diagkit/gather/diagnose.walkOnce(0x108a960?, 0xc0002df890)
[ common/pkg/diagkit/gather/diagnose/run.go:135 +0xcc
[common/pkg/diagkit/gather/diagnose.Run(0x16bfea0, 0x1084300?, {0xc0002dfb20, 0x1, 0x1})
[ common/pkg/diagkit/gather/diagnose/run.go:16 +0x1cb
[main.checkCmd({0xc0000963b0?, 0xc0000963b0?, 0x4?}, {0x0, 0x0})
[ common/cmd/com.docker.diagnose/main.go:132 +0x105
[main.main()
[ common/cmd/com.docker.diagnose/main.go:98 +0x27f
[2022-06-25T08:41:28.687231000Z][com.docker.diagnose.exe][I] (f57069bc) 8a63a04d-diagnose C->S diagnosticsd GET /ping
[2022-06-25T08:41:28.687766200Z][com.docker.diagnose.exe][W] (f57069bc) 8a63a04d-diagnose C<-S NoResponse GET /ping (535.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] 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:
* vpnkit-bridge.exe is not running
* vpnkit.exe is not running
* com.docker.proxy.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\dockerDesktopLinuxEngine: The system cannot find the file specified.
[2022-06-25T08:41:37.851910300Z][com.docker.diagnose.exe][I] ipc.NewClient: b806a430-diagnose -> \\.\pipe\dockerDesktopLinuxEngine Proxy
[common/pkg/diagkit/gather/diagnose.glob..func12()
[ common/pkg/diagkit/gather/diagnose/ipc.go:91 +0x7e
[common/pkg/diagkit/gather/diagnose.(*test).GetResult(0x16bfba0)
[ common/pkg/diagkit/gather/diagnose/test.go:46 +0x43
[common/pkg/diagkit/gather/diagnose.Run.func1(0x16bfba0)
[ common/pkg/diagkit/gather/diagnose/run.go:17 +0x5a
[common/pkg/diagkit/gather/diagnose.walkOnce.func1(0x2?, 0x16bfba0)
[ common/pkg/diagkit/gather/diagnose/run.go:140 +0x77
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x1, 0x16bfba0, 0xc0005a3730)
[ common/pkg/diagkit/gather/diagnose/run.go:146 +0x36
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x0, 0xcb00000012?, 0xc0005a3730)
[ common/pkg/diagkit/gather/diagnose/run.go:149 +0x73
[common/pkg/diagkit/gather/diagnose.walkOnce(0x108a960?, 0xc0002df890)
[ common/pkg/diagkit/gather/diagnose/run.go:135 +0xcc
[common/pkg/diagkit/gather/diagnose.Run(0x16bfea0, 0x1084300?, {0xc0002dfb20, 0x1, 0x1})
[ common/pkg/diagkit/gather/diagnose/run.go:16 +0x1cb
[main.checkCmd({0xc0000963b0?, 0xc0000963b0?, 0x4?}, {0x0, 0x0})
[ common/cmd/com.docker.diagnose/main.go:132 +0x105
[main.main()
[ common/cmd/com.docker.diagnose/main.go:98 +0x27f
[2022-06-25T08:41:37.851910300Z][com.docker.diagnose.exe][I] (12527d67) b806a430-diagnose C->S Proxy GET /desktop-diagnostics/ping
[2022-06-25T08:41:37.851910300Z][com.docker.diagnose.exe][W] (12527d67) b806a430-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.
[2022-06-25T08:41:37.852446500Z][com.docker.diagnose.exe][I] (12527d67-1) b806a430-diagnose C->S Proxy GET /ping
[2022-06-25T08:41:37.852446500Z][com.docker.diagnose.exe][W] (12527d67-1) b806a430-diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \\.\pipe\dockerDesktopLinuxEngine: The system cannot find the file specified.
[2022-06-25T08:41:38.856943100Z][com.docker.diagnose.exe][I] (12527d67-2) b806a430-diagnose C->S Proxy GET /ping
[2022-06-25T08:41:38.857076000Z][com.docker.diagnose.exe][W] (12527d67-2) b806a430-diagnose C<-S NoResponse GET /ping (237.5µs): Get "http://ipc/ping": open \\.\pipe\dockerDesktopLinuxEngine: The system cannot find the file specified.
[2022-06-25T08:41:39.860294800Z][com.docker.diagnose.exe][I] (12527d67-3) b806a430-diagnose C->S Proxy GET /ping
[2022-06-25T08:41:39.860294800Z][com.docker.diagnose.exe][W] (12527d67-3) b806a430-diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \\.\pipe\dockerDesktopLinuxEngine: The system cannot find the file specified.
[2022-06-25T08:41:40.866426100Z][com.docker.diagnose.exe][I] (12527d67-4) b806a430-diagnose C->S Proxy GET /ping
[2022-06-25T08:41:40.866866800Z][com.docker.diagnose.exe][W] (12527d67-4) b806a430-diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \\.\pipe\dockerDesktopLinuxEngine: The system cannot find the file specified.
[2022-06-25T08:41:41.869246800Z][com.docker.diagnose.exe][I] (12527d67-5) b806a430-diagnose C->S Proxy GET /ping
[2022-06-25T08:41:41.869246800Z][com.docker.diagnose.exe][W] (12527d67-5) b806a430-diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \\.\pipe\dockerDesktopLinuxEngine: The system cannot find the file specified.
[2022-06-25T08:41:42.872845200Z][com.docker.diagnose.exe][I] (12527d67-6) b806a430-diagnose C->S Proxy GET /ping
[2022-06-25T08:41:42.872845200Z][com.docker.diagnose.exe][W] (12527d67-6) b806a430-diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \\.\pipe\dockerDesktopLinuxEngine: The system cannot find the file specified.
[2022-06-25T08:41:43.874787600Z][com.docker.diagnose.exe][I] (12527d67-7) b806a430-diagnose C->S Proxy GET /ping
[2022-06-25T08:41:43.874787600Z][com.docker.diagnose.exe][W] (12527d67-7) b806a430-diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \\.\pipe\dockerDesktopLinuxEngine: The system cannot find the file specified.
[2022-06-25T08:41:44.879214700Z][com.docker.diagnose.exe][I] (12527d67-8) b806a430-diagnose C->S Proxy GET /ping
[2022-06-25T08:41:44.879214700Z][com.docker.diagnose.exe][W] (12527d67-8) b806a430-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.
[2022-06-25T08:41:44.932117000Z][com.docker.diagnose.exe][I] ipc.NewClient: e4e40e7e-diagnose-network -> \\.\pipe\dockerDiagnosticd diagnosticsd
[common/pkg/diagkit/gather/diagnose.runIsVMNetworkingOK()
[ common/pkg/diagkit/gather/diagnose/network.go:34 +0xdd
[common/pkg/diagkit/gather/diagnose.(*test).GetResult(0x16bf8a0)
[ common/pkg/diagkit/gather/diagnose/test.go:46 +0x43
[common/pkg/diagkit/gather/diagnose.Run.func1(0x16bf8a0)
[ common/pkg/diagkit/gather/diagnose/run.go:17 +0x5a
[common/pkg/diagkit/gather/diagnose.walkOnce.func1(0x2?, 0x16bf8a0)
[ common/pkg/diagkit/gather/diagnose/run.go:140 +0x77
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x1, 0x16bf8a0, 0xc000515730)
[ common/pkg/diagkit/gather/diagnose/run.go:146 +0x36
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x0, 0xcb00000012?, 0xc000515730)
[ common/pkg/diagkit/gather/diagnose/run.go:149 +0x73
[common/pkg/diagkit/gather/diagnose.walkOnce(0x108a960?, 0xc0002df890)
[ common/pkg/diagkit/gather/diagnose/run.go:135 +0xcc
[common/pkg/diagkit/gather/diagnose.Run(0x16bfea0, 0x1084300?, {0xc0002dfb20, 0x1, 0x1})
[ common/pkg/diagkit/gather/diagnose/run.go:16 +0x1cb
[main.checkCmd({0xc0000963b0?, 0xc0000963b0?, 0x4?}, {0x0, 0x0})
[ common/cmd/com.docker.diagnose/main.go:132 +0x105
[main.main()
[ common/cmd/com.docker.diagnose/main.go:98 +0x27f
[2022-06-25T08:41:44.932117000Z][com.docker.diagnose.exe][I] (7693a3f6) e4e40e7e-diagnose-network C->S diagnosticsd POST /check-network-connectivity: {"ips":["10.43.232.55","172.31.192.1","172.17.240.1"]}
[2022-06-25T08:41:44.932619500Z][com.docker.diagnose.exe][W] (7693a3f6) e4e40e7e-diagnose-network C<-S NoResponse POST /check-network-connectivity (502.5µs): Post "http://ipc/check-network-connectivity": open \\.\pipe\dockerDiagnosticd: The system cannot find the file specified.
[2022-06-25T08:41:44.932619500Z][com.docker.diagnose.exe][I] (7693a3f6-1) e4e40e7e-diagnose-network C->S diagnosticsd GET /ping
[2022-06-25T08:41:44.932619500Z][com.docker.diagnose.exe][W] (7693a3f6-1) e4e40e7e-diagnose-network C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \\.\pipe\dockerDiagnosticd: The system cannot find the file specified.
[2022-06-25T08:41:45.944445800Z][com.docker.diagnose.exe][I] (7693a3f6-2) e4e40e7e-diagnose-network C->S diagnosticsd GET /ping
[2022-06-25T08:41:45.944445800Z][com.docker.diagnose.exe][W] (7693a3f6-2) e4e40e7e-diagnose-network C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \\.\pipe\dockerDiagnosticd: The system cannot find the file specified.
[2022-06-25T08:41:46.950724700Z][com.docker.diagnose.exe][I] (7693a3f6-3) e4e40e7e-diagnose-network C->S diagnosticsd GET /ping
[2022-06-25T08:41:46.950896000Z][com.docker.diagnose.exe][W] (7693a3f6-3) e4e40e7e-diagnose-network C<-S NoResponse GET /ping (171.3µs): Get "http://ipc/ping": open \\.\pipe\dockerDiagnosticd: The system cannot find the file specified.
[2022-06-25T08:41:47.954482700Z][com.docker.diagnose.exe][I] (7693a3f6-4) e4e40e7e-diagnose-network C->S diagnosticsd GET /ping
[2022-06-25T08:41:47.954482700Z][com.docker.diagnose.exe][W] (7693a3f6-4) e4e40e7e-diagnose-network C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \\.\pipe\dockerDiagnosticd: The system cannot find the file specified.
[2022-06-25T08:41:48.959128300Z][com.docker.diagnose.exe][I] (7693a3f6-5) e4e40e7e-diagnose-network C->S diagnosticsd GET /ping
[2022-06-25T08:41:48.959376500Z][com.docker.diagnose.exe][W] (7693a3f6-5) e4e40e7e-diagnose-network C<-S NoResponse GET /ping (248.2µs): Get "http://ipc/ping": open \\.\pipe\dockerDiagnosticd: The system cannot find the file specified.
[2022-06-25T08:41:49.959410900Z][com.docker.diagnose.exe][I] (7693a3f6-6) e4e40e7e-diagnose-network C->S diagnosticsd GET /ping
[2022-06-25T08:41:49.959510300Z][com.docker.diagnose.exe][W] (7693a3f6-6) e4e40e7e-diagnose-network C<-S NoResponse GET /ping (99.4µs): Get "http://ipc/ping": open \\.\pipe\dockerDiagnosticd: The system cannot find the file specified.
[2022-06-25T08:41:50.964341700Z][com.docker.diagnose.exe][I] (7693a3f6-7) e4e40e7e-diagnose-network C->S diagnosticsd GET /ping
[2022-06-25T08:41:50.964341700Z][com.docker.diagnose.exe][W] (7693a3f6-7) e4e40e7e-diagnose-network C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \\.\pipe\dockerDiagnosticd: The system cannot find the file specified.
[2022-06-25T08:41:51.970176000Z][com.docker.diagnose.exe][I] (7693a3f6-8) e4e40e7e-diagnose-network C->S diagnosticsd GET /ping
[2022-06-25T08:41:51.970176000Z][com.docker.diagnose.exe][W] (7693a3f6-8) e4e40e7e-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 3 issues:
1 : 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.
2 : The test: are the backend processes running?
Failed with: 3 errors occurred:
* vpnkit-bridge.exe is not running
* vpnkit.exe is not running
* com.docker.proxy.exe is not running
Not all of the backend processes are running.
3 : 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.
PS C:\Program Files\Docker\Docker\resources>
```
This is after I click `restart wsl2 backend`
```cmd
PS C:\Program Files\Docker\Docker\resources> .\com.docker.diagnose.exe check
Starting diagnostics
[PASS] DD0027: is there available disk space on the host?
[PASS] DD0028: is there available VM disk space?
[PASS] DD0031: does the Docker API work?
[PASS] DD0004: is the Docker engine running?
[PASS] DD0011: are the LinuxKit services running?
[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] DD0015: are the binary symlinks installed?
[PASS] DD0003: is the Docker CLI working?
[PASS] DD0013: is the $PATH ok?
[PASS] DD0005: is the user in the docker-users group?
[PASS] DD0007: is the backend responding?
[PASS] DD0014: are the backend processes running?
[PASS] DD0008: is the native API responding?
[PASS] DD0009: is the vpnkit API responding?
[PASS] DD0010: is the Docker API proxy responding?
[PASS] DD0006: is the Docker Desktop Service responding?
[FAIL] DD0012: is the VM networking working? network checks failed: failed to ping host: exit status 1
[2022-06-25T08:38:47.517186500Z][com.docker.diagnose.exe][I] ipc.NewClient: d68ea00e-diagnose-network -> \\.\pipe\dockerDiagnosticd diagnosticsd
[common/pkg/diagkit/gather/diagnose.runIsVMNetworkingOK()
[ common/pkg/diagkit/gather/diagnose/network.go:34 +0xdd
[common/pkg/diagkit/gather/diagnose.(*test).GetResult(0x16bf8a0)
[ common/pkg/diagkit/gather/diagnose/test.go:46 +0x43
[common/pkg/diagkit/gather/diagnose.Run.func1(0x16bf8a0)
[ common/pkg/diagkit/gather/diagnose/run.go:17 +0x5a
[common/pkg/diagkit/gather/diagnose.walkOnce.func1(0x2?, 0x16bf8a0)
[ common/pkg/diagkit/gather/diagnose/run.go:140 +0x77
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x1, 0x16bf8a0, 0xc00058d730)
[ common/pkg/diagkit/gather/diagnose/run.go:146 +0x36
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x0, 0xcb00000012?, 0xc00058d730)
[ common/pkg/diagkit/gather/diagnose/run.go:149 +0x73
[common/pkg/diagkit/gather/diagnose.walkOnce(0x108a960?, 0xc0002df890)
[ common/pkg/diagkit/gather/diagnose/run.go:135 +0xcc
[common/pkg/diagkit/gather/diagnose.Run(0x16bfea0, 0x1084300?, {0xc0002dfb20, 0x1, 0x1})
[ common/pkg/diagkit/gather/diagnose/run.go:16 +0x1cb
[main.checkCmd({0xc0000983b0?, 0xc0000983b0?, 0x4?}, {0x0, 0x0})
[ common/cmd/com.docker.diagnose/main.go:132 +0x105
[main.main()
[ common/cmd/com.docker.diagnose/main.go:98 +0x27f
[2022-06-25T08:38:47.517186500Z][com.docker.diagnose.exe][I] (e08cec47) d68ea00e-diagnose-network C->S diagnosticsd POST /check-network-connectivity: {"ips":["10.43.232.55","172.31.192.1","172.17.240.1"]}
[2022-06-25T08:38:48.043847800Z][com.docker.diagnose.exe][W] (e08cec47) d68ea00e-diagnose-network C<-S 184822ad-diagnosticsd POST /check-network-connectivity (526.6636ms): failed to ping host: exit status 1
[FAIL] DD0032: do Docker networks overlap with host IPs? network bridge has subnet 172.17.0.0/16 which overlaps with host IP 172.17.240.1
[SKIP] DD0030: is the image access management authorized?
[PASS] DD0033: does the host have Internet access?
Please investigate the following 2 issues:
1 : The test: is the VM networking working?
Failed with: network checks failed: failed to ping host: exit status 1
VM seems to have a network connectivity issue. Please check your host firewall and anti-virus settings in case they are blocking the VM.
2 : The test: do Docker networks overlap with host IPs?
Failed with: network bridge has subnet 172.17.0.0/16 which overlaps with host IP 172.17.240.1
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.
Please 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
PS C:\Program Files\Docker\Docker\resources>
```
### Steps to reproduce the behavior
<!--
A reproducible case, Dockerfiles with reproduction inside is best.
-->
just run `docker build -t xxx:v1 .`