search

docker / for-win

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

Docker 4.18 Fails to Start After Latest WSL Update #13391

Open groogiam opened 1 year ago

groogiam commented 1 year ago

Actual behavior

Docker desktop does not start when trying to run at machine startup via windows scheduler. This worked without issue until yesterday. It looks like it now fails to start WSL. I have also run into issues even with the GUI running.

Expected behavior

Docker should start.

Information

[PASS] DD0027: is there available disk space on the host? [PASS] DD0028: is there available VM disk space? [FAIL] DD0002: does the bootloader have virtualization enabled? contacting Windows service: Get "http://ipc/hyperv/bootloader": open \.\pipe\dockerBackendV2: The system cannot find the file specified. [2023-04-12T22:19:26.298932800Z][com.docker.diagnose.exe][I] ipc.NewClient: 418db540-com.docker.diagnose -> \.\pipe\dockerBackendV2 com.docker.service [2023-04-12T22:19:26.299992000Z][com.docker.diagnose.exe][I] (c60dec95) 418db540-com.docker.diagnose C->S com.docker.service GET /hyperv/bootloader [2023-04-12T22:19:26.300514100Z][com.docker.diagnose.exe][W] (c60dec95) 418db540-com.docker.diagnose C<-S NoResponse GET /hyperv/bootloader (522.1µs): Get "http://ipc/hyperv/bootloader": open \.\pipe\dockerBackendV2: The system cannot find the file specified. [2023-04-12T22:19:26.301038600Z][com.docker.diagnose.exe][I] (c60dec95-1) 418db540-com.docker.diagnose C->S com.docker.service GET /ping [2023-04-12T22:19:26.301038600Z][com.docker.diagnose.exe][W] (c60dec95-1) 418db540-com.docker.diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \.\pipe\dockerBackendV2: The system cannot find the file specified. [2023-04-12T22:19:27.305336400Z][com.docker.diagnose.exe][I] (c60dec95-2) 418db540-com.docker.diagnose C->S com.docker.service GET /ping [2023-04-12T22:19:27.305944500Z][com.docker.diagnose.exe][W] (c60dec95-2) 418db540-com.docker.diagnose C<-S NoResponse GET /ping (608.1µs): Get "http://ipc/ping": open \.\pipe\dockerBackendV2: The system cannot find the file specified. [2023-04-12T22:19:28.322338700Z][com.docker.diagnose.exe][I] (c60dec95-3) 418db540-com.docker.diagnose C->S com.docker.service GET /ping [2023-04-12T22:19:28.322964100Z][com.docker.diagnose.exe][W] (c60dec95-3) 418db540-com.docker.diagnose C<-S NoResponse GET /ping (787.1µs): Get "http://ipc/ping": open \.\pipe\dockerBackendV2: The system cannot find the file specified. [2023-04-12T22:19:29.332623800Z][com.docker.diagnose.exe][I] (c60dec95-4) 418db540-com.docker.diagnose C->S com.docker.service GET /ping [2023-04-12T22:19:29.332912200Z][com.docker.diagnose.exe][W] (c60dec95-4) 418db540-com.docker.diagnose C<-S NoResponse GET /ping (288.4µs): Get "http://ipc/ping": open \.\pipe\dockerBackendV2: The system cannot find the file specified. [2023-04-12T22:19:30.339159700Z][com.docker.diagnose.exe][I] (c60dec95-5) 418db540-com.docker.diagnose C->S com.docker.service GET /ping [2023-04-12T22:19:30.339746800Z][com.docker.diagnose.exe][W] (c60dec95-5) 418db540-com.docker.diagnose C<-S NoResponse GET /ping (587.1µs): Get "http://ipc/ping": open \.\pipe\dockerBackendV2: The system cannot find the file specified. [2023-04-12T22:19:31.341232000Z][com.docker.diagnose.exe][I] (c60dec95-6) 418db540-com.docker.diagnose C->S com.docker.service GET /ping [2023-04-12T22:19:31.341740400Z][com.docker.diagnose.exe][W] (c60dec95-6) 418db540-com.docker.diagnose C<-S NoResponse GET /ping (508.4µs): Get "http://ipc/ping": open \.\pipe\dockerBackendV2: The system cannot find the file specified. [2023-04-12T22:19:32.342354300Z][com.docker.diagnose.exe][I] (c60dec95-7) 418db540-com.docker.diagnose C->S com.docker.service GET /ping [2023-04-12T22:19:32.342954100Z][com.docker.diagnose.exe][W] (c60dec95-7) 418db540-com.docker.diagnose C<-S NoResponse GET /ping (599.8µs): Get "http://ipc/ping": open \.\pipe\dockerBackendV2: The system cannot find the file specified. [2023-04-12T22:19:33.351776500Z][com.docker.diagnose.exe][I] (c60dec95-8) 418db540-com.docker.diagnose C->S com.docker.service GET /ping [2023-04-12T22:19:33.352299900Z][com.docker.diagnose.exe][W] (c60dec95-8) 418db540-com.docker.diagnose C<-S NoResponse GET /ping (523.4µs): Get "http://ipc/ping": open \.\pipe\dockerBackendV2: The system cannot find the file specified.

[SKIP] DD0018: does the host support virtualization? [PASS] DD0001: is the application running? [FAIL] DD0022: is the Virtual Machine Platform Windows Feature enabled? querying windows features: Post "http://ipc/windowsfeatures/check": open \.\pipe\dockerBackendV2: The system cannot find the file specified. [2023-04-12T22:19:33.362320200Z][com.docker.diagnose.exe][I] ipc.NewClient: fdccdb79-com.docker.diagnose -> \.\pipe\dockerBackendV2 com.docker.service [2023-04-12T22:19:33.362853900Z][com.docker.diagnose.exe][I] (3b0df08c) fdccdb79-com.docker.diagnose C->S com.docker.service POST /windowsfeatures/check: [VirtualMachinePlatform (Virtual Machine Platform)] [2023-04-12T22:19:33.363378800Z][com.docker.diagnose.exe][W] (3b0df08c) fdccdb79-com.docker.diagnose C<-S NoResponse POST /windowsfeatures/check (524.9µs): Post "http://ipc/windowsfeatures/check": open \.\pipe\dockerBackendV2: The system cannot find the file specified. [2023-04-12T22:19:33.363909700Z][com.docker.diagnose.exe][I] (3b0df08c-1) fdccdb79-com.docker.diagnose C->S com.docker.service GET /ping [2023-04-12T22:19:33.363909700Z][com.docker.diagnose.exe][W] (3b0df08c-1) fdccdb79-com.docker.diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \.\pipe\dockerBackendV2: The system cannot find the file specified. [2023-04-12T22:19:34.369826100Z][com.docker.diagnose.exe][I] (3b0df08c-2) fdccdb79-com.docker.diagnose C->S com.docker.service GET /ping [2023-04-12T22:19:34.370434600Z][com.docker.diagnose.exe][W] (3b0df08c-2) fdccdb79-com.docker.diagnose C<-S NoResponse GET /ping (608.5µs): Get "http://ipc/ping": open \.\pipe\dockerBackendV2: The system cannot find the file specified. [2023-04-12T22:19:35.374087900Z][com.docker.diagnose.exe][I] (3b0df08c-3) fdccdb79-com.docker.diagnose C->S com.docker.service GET /ping [2023-04-12T22:19:35.374677000Z][com.docker.diagnose.exe][W] (3b0df08c-3) fdccdb79-com.docker.diagnose C<-S NoResponse GET /ping (589.1µs): Get "http://ipc/ping": open \.\pipe\dockerBackendV2: The system cannot find the file specified. [2023-04-12T22:19:36.375935600Z][com.docker.diagnose.exe][I] (3b0df08c-4) fdccdb79-com.docker.diagnose C->S com.docker.service GET /ping [2023-04-12T22:19:36.376458600Z][com.docker.diagnose.exe][W] (3b0df08c-4) fdccdb79-com.docker.diagnose C<-S NoResponse GET /ping (523µs): Get "http://ipc/ping": open \.\pipe\dockerBackendV2: The system cannot find the file specified. [2023-04-12T22:19:37.383720800Z][com.docker.diagnose.exe][I] (3b0df08c-5) fdccdb79-com.docker.diagnose C->S com.docker.service GET /ping [2023-04-12T22:19:37.384339900Z][com.docker.diagnose.exe][W] (3b0df08c-5) fdccdb79-com.docker.diagnose C<-S NoResponse GET /ping (619.1µs): Get "http://ipc/ping": open \.\pipe\dockerBackendV2: The system cannot find the file specified. [2023-04-12T22:19:38.392851400Z][com.docker.diagnose.exe][I] (3b0df08c-6) fdccdb79-com.docker.diagnose C->S com.docker.service GET /ping [2023-04-12T22:19:38.394156800Z][com.docker.diagnose.exe][W] (3b0df08c-6) fdccdb79-com.docker.diagnose C<-S NoResponse GET /ping (1.3056ms): Get "http://ipc/ping": open \.\pipe\dockerBackendV2: The system cannot find the file specified. [2023-04-12T22:19:39.409844300Z][com.docker.diagnose.exe][I] (3b0df08c-7) fdccdb79-com.docker.diagnose C->S com.docker.service GET /ping [2023-04-12T22:19:39.410367200Z][com.docker.diagnose.exe][W] (3b0df08c-7) fdccdb79-com.docker.diagnose C<-S NoResponse GET /ping (523µs): Get "http://ipc/ping": open \.\pipe\dockerBackendV2: The system cannot find the file specified. [2023-04-12T22:19:40.426249300Z][com.docker.diagnose.exe][I] (3b0df08c-8) fdccdb79-com.docker.diagnose C->S com.docker.service GET /ping [2023-04-12T22:19:40.426249300Z][com.docker.diagnose.exe][W] (3b0df08c-8) fdccdb79-com.docker.diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \.\pipe\dockerBackendV2: The system cannot find the file specified.

[FAIL] DD0021: is the WSL 2 Windows Feature enabled? querying windows features: Post "http://ipc/windowsfeatures/check": open \.\pipe\dockerBackendV2: The system cannot find the file specified. [2023-04-12T22:19:40.428299300Z][com.docker.diagnose.exe][I] ipc.NewClient: e9222488-com.docker.diagnose -> \.\pipe\dockerBackendV2 com.docker.service [2023-04-12T22:19:40.428921500Z][com.docker.diagnose.exe][I] (ead1ffe5) e9222488-com.docker.diagnose C->S com.docker.service POST /windowsfeatures/check: [Microsoft-Windows-Subsystem-Linux (Windows Subsystem for Linux)] [2023-04-12T22:19:40.429426300Z][com.docker.diagnose.exe][W] (ead1ffe5) e9222488-com.docker.diagnose C<-S NoResponse POST /windowsfeatures/check (504.9µs): Post "http://ipc/windowsfeatures/check": open \.\pipe\dockerBackendV2: The system cannot find the file specified. [2023-04-12T22:19:40.429968700Z][com.docker.diagnose.exe][I] (ead1ffe5-1) e9222488-com.docker.diagnose C->S com.docker.service GET /ping [2023-04-12T22:19:40.430505900Z][com.docker.diagnose.exe][W] (ead1ffe5-1) e9222488-com.docker.diagnose C<-S NoResponse GET /ping (537.3µs): Get "http://ipc/ping": open \.\pipe\dockerBackendV2: The system cannot find the file specified. [2023-04-12T22:19:41.432272500Z][com.docker.diagnose.exe][I] (ead1ffe5-2) e9222488-com.docker.diagnose C->S com.docker.service GET /ping [2023-04-12T22:19:41.432955200Z][com.docker.diagnose.exe][W] (ead1ffe5-2) e9222488-com.docker.diagnose C<-S NoResponse GET /ping (682.8µs): Get "http://ipc/ping": open \.\pipe\dockerBackendV2: The system cannot find the file specified. [2023-04-12T22:19:42.444465900Z][com.docker.diagnose.exe][I] (ead1ffe5-3) e9222488-com.docker.diagnose C->S com.docker.service GET /ping [2023-04-12T22:19:42.445076000Z][com.docker.diagnose.exe][W] (ead1ffe5-3) e9222488-com.docker.diagnose C<-S NoResponse GET /ping (610.2µs): Get "http://ipc/ping": open \.\pipe\dockerBackendV2: The system cannot find the file specified. [2023-04-12T22:19:43.460118800Z][com.docker.diagnose.exe][I] (ead1ffe5-4) e9222488-com.docker.diagnose C->S com.docker.service GET /ping [2023-04-12T22:19:43.460801400Z][com.docker.diagnose.exe][W] (ead1ffe5-4) e9222488-com.docker.diagnose C<-S NoResponse GET /ping (682.7µs): Get "http://ipc/ping": open \.\pipe\dockerBackendV2: The system cannot find the file specified. [2023-04-12T22:19:44.476603500Z][com.docker.diagnose.exe][I] (ead1ffe5-5) e9222488-com.docker.diagnose C->S com.docker.service GET /ping [2023-04-12T22:19:44.480721900Z][com.docker.diagnose.exe][W] (ead1ffe5-5) e9222488-com.docker.diagnose C<-S NoResponse GET /ping (4.1192ms): Get "http://ipc/ping": open \.\pipe\dockerBackendV2: The system cannot find the file specified. [2023-04-12T22:19:45.491161200Z][com.docker.diagnose.exe][I] (ead1ffe5-6) e9222488-com.docker.diagnose C->S com.docker.service GET /ping [2023-04-12T22:19:45.492057600Z][com.docker.diagnose.exe][W] (ead1ffe5-6) e9222488-com.docker.diagnose C<-S NoResponse GET /ping (896.5µs): Get "http://ipc/ping": open \.\pipe\dockerBackendV2: The system cannot find the file specified. [2023-04-12T22:19:46.496726400Z][com.docker.diagnose.exe][I] (ead1ffe5-7) e9222488-com.docker.diagnose C->S com.docker.service GET /ping [2023-04-12T22:19:46.497387800Z][com.docker.diagnose.exe][W] (ead1ffe5-7) e9222488-com.docker.diagnose C<-S NoResponse GET /ping (661.5µs): Get "http://ipc/ping": open \.\pipe\dockerBackendV2: The system cannot find the file specified. [2023-04-12T22:19:47.509210100Z][com.docker.diagnose.exe][I] (ead1ffe5-8) e9222488-com.docker.diagnose C->S com.docker.service GET /ping [2023-04-12T22:19:47.510843800Z][com.docker.diagnose.exe][W] (ead1ffe5-8) e9222488-com.docker.diagnose C<-S NoResponse GET /ping (1.634ms): Get "http://ipc/ping": open \.\pipe\dockerBackendV2: The system cannot find the file specified.

[PASS] DD0024: is WSL installed? [PASS] DD0025: are WSL distros installed? [PASS] DD0026: is the WSL LxssManager service running? [FAIL] DD0029: is the WSL 2 Linux filesystem corrupt? exit status 0xffffffff [FAIL] DD0035: is the VM time synchronized? exit status 0xffffffff [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-12T22:19:47.856624500Z][com.docker.diagnose.exe][I] ipc.NewClient: 2728e5c0-diagnose -> \.\pipe\dockerDiagnosticd diagnosticsd [2023-04-12T22:19:47.857158100Z][com.docker.diagnose.exe][I] (5815d3ff) 2728e5c0-diagnose C->S diagnosticsd GET /ping [2023-04-12T22:19:47.857158100Z][com.docker.diagnose.exe][W] (5815d3ff) 2728e5c0-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-12T22:19:47.857679300Z][com.docker.diagnose.exe][I] ipc.NewClient: 8cb1b28b-com.docker.diagnose -> \.\pipe\dockerLifecycleServer VMDockerdAPI [2023-04-12T22:19:47.858199700Z][com.docker.diagnose.exe][I] (90a3423d) 8cb1b28b-com.docker.diagnose C->S VMDockerdAPI GET /docker [2023-04-12T22:19:47.858199700Z][com.docker.diagnose.exe][W] (90a3423d) 8cb1b28b-com.docker.diagnose C<-S NoResponse GET /docker (0s): Get "http://ipc/docker": open \.\pipe\dockerLifecycleServer: The system cannot find the file specified. [2023-04-12T22:19:47.858199700Z][com.docker.diagnose.exe][I] (90a3423d-1) 8cb1b28b-com.docker.diagnose C->S VMDockerdAPI GET /ping [2023-04-12T22:19:47.858720700Z][com.docker.diagnose.exe][W] (90a3423d-1) 8cb1b28b-com.docker.diagnose C<-S NoResponse GET /ping (521.1µs): Get "http://ipc/ping": open \.\pipe\dockerLifecycleServer: The system cannot find the file specified. [2023-04-12T22:19:48.872942300Z][com.docker.diagnose.exe][I] (90a3423d-2) 8cb1b28b-com.docker.diagnose C->S VMDockerdAPI GET /ping [2023-04-12T22:19:48.873465200Z][com.docker.diagnose.exe][W] (90a3423d-2) 8cb1b28b-com.docker.diagnose C<-S NoResponse GET /ping (758µs): Get "http://ipc/ping": open \.\pipe\dockerLifecycleServer: The system cannot find the file specified. [2023-04-12T22:19:49.882487400Z][com.docker.diagnose.exe][I] (90a3423d-3) 8cb1b28b-com.docker.diagnose C->S VMDockerdAPI GET /ping [2023-04-12T22:19:49.882487400Z][com.docker.diagnose.exe][W] (90a3423d-3) 8cb1b28b-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-12T22:19:50.883471700Z][com.docker.diagnose.exe][I] (90a3423d-4) 8cb1b28b-com.docker.diagnose C->S VMDockerdAPI GET /ping [2023-04-12T22:19:50.883979300Z][com.docker.diagnose.exe][W] (90a3423d-4) 8cb1b28b-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-12T22:19:51.887221900Z][com.docker.diagnose.exe][I] (90a3423d-5) 8cb1b28b-com.docker.diagnose C->S VMDockerdAPI GET /ping [2023-04-12T22:19:51.887928000Z][com.docker.diagnose.exe][W] (90a3423d-5) 8cb1b28b-com.docker.diagnose C<-S NoResponse GET /ping (706.2µs): Get "http://ipc/ping": open \.\pipe\dockerLifecycleServer: The system cannot find the file specified. [2023-04-12T22:19:52.892567600Z][com.docker.diagnose.exe][I] (90a3423d-6) 8cb1b28b-com.docker.diagnose C->S VMDockerdAPI GET /ping [2023-04-12T22:19:52.893226000Z][com.docker.diagnose.exe][W] (90a3423d-6) 8cb1b28b-com.docker.diagnose C<-S NoResponse GET /ping (658.5µs): Get "http://ipc/ping": open \.\pipe\dockerLifecycleServer: The system cannot find the file specified. [2023-04-12T22:19:53.895650100Z][com.docker.diagnose.exe][I] (90a3423d-7) 8cb1b28b-com.docker.diagnose C->S VMDockerdAPI GET /ping [2023-04-12T22:19:53.896463800Z][com.docker.diagnose.exe][W] (90a3423d-7) 8cb1b28b-com.docker.diagnose C<-S NoResponse GET /ping (813.9µs): Get "http://ipc/ping": open \.\pipe\dockerLifecycleServer: The system cannot find the file specified. [2023-04-12T22:19:54.900733200Z][com.docker.diagnose.exe][I] (90a3423d-8) 8cb1b28b-com.docker.diagnose C->S VMDockerdAPI GET /ping [2023-04-12T22:19:54.901252800Z][com.docker.diagnose.exe][W] (90a3423d-8) 8cb1b28b-com.docker.diagnose C<-S NoResponse GET /ping (519.7µs): 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 [PASS] DD0005: is the user in the docker-users group? [PASS] DD0038: is the connection to Docker working? 2023/04/12 18:19:56 error checking if default wsl distro is running: exit status 0xffffffff

Steps to reproduce the behavior

  1. ...
  2. ...
maikebing commented 1 year ago

https://github.com/microsoft/WSL/issues/5895#issuecomment-1506847178

erkenes commented 1 year ago

Possible workaround

The newest WSL update occured this issue. The issue took me multiple hours to "fix".

You can install the the following release of WSL manually from here: https://github.com/microsoft/WSL/releases/tag/1.1.3 Just download the msixbundle-File and install it. After that Docker Desktop works again. This release was re-marked as "latest" in GitHub. The Microsoft Store install the Version 1.2.0 which occurs the issues.

The command wsl --update --pre-release does not resolve the issue.

groogiam commented 1 year ago

@erkenes Thanks for the possible work around. This works when running docker from a desktop with an interactive console but still fails if docker desktop is launched at boot from the task scheduler.

jkxbest commented 1 year ago

@erkenes Thanks for your advice, there is no problem with the stable version of wsl, I have blocked the wsl update of Microsoft Store, because it is a ghost

saidas3524 commented 1 year ago

I am facing this issue too with docker desktop 4.18. Multiple reinstallations did not work.

jseaber commented 1 year ago

Possible workaround

The newest WSL update occured this issue. The issue took me multiple hours to "fix".

You can install the the following release of WSL manually from here: https://github.com/microsoft/WSL/releases/tag/1.1.3 Just download the msixbundle-File and install it. After that Docker Desktop works again. This release was re-marked as "latest" in GitHub. The Microsoft Store install the Version 1.2.0 which occurs the issues.

The command wsl --update --pre-release does not resolve the issue.

Thanks! Installing WSL v1.1.3 seems to have resolved here.