CLI not working, loader never stops service is running

[tyoc213]

• I have tried with the latest version of Docker Desktop
• I have tried disabling enabled experimental features
• I have uploaded Diagnostics
• Diagnostics ID: 7FF56726-C0D1-4352-8D17-9AFA026FEDD3/20230409194116

Actual behavior

Docker is not running but did not fail to install so I guess it didnt detect any missing prerequisite.

Expected behavior

Be able to run docker run hello-world

Information

• Windows Version: home 11
• Docker Desktop Version: 20.10.24, build 297e128
• WSL2 or Hyper-V backend? WSL2
• Are you running inside a virtualized Windows e.g. on a cloud server or a VM: In a GPD win max 2

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

& "C:\Program Files\Docker\Docker\resources\com.docker.diagnose.exe" check
[2023-04-09T20:11:35.759117500Z][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?
[FAIL] DD0035: is the VM time synchronized? parsing time output: 2023-04-09T20:11:44+00:00: parsing time "2023-04-09T20:11:44+00:00" as "2006-01-02T15:04:05UTC": cannot parse "+00:00" as "UTC"
[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-09T20:11:44.990864200Z][com.docker.diagnose.exe][I] ipc.NewClient: 0e2bfe3c-diagnose -> \\.\pipe\dockerDiagnosticd diagnosticsd
[2023-04-09T20:11:44.992000700Z][com.docker.diagnose.exe][I] (ccdc87df) 0e2bfe3c-diagnose C->S diagnosticsd GET /ping
[2023-04-09T20:11:44.993115900Z][com.docker.diagnose.exe][W] (ccdc87df) 0e2bfe3c-diagnose C<-S NoResponse GET /ping (1.1153ms): 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-09T20:11:44.994177600Z][com.docker.diagnose.exe][I] ipc.NewClient: 00a63479-com.docker.diagnose -> \\.\pipe\dockerLifecycleServer VMDockerdAPI
[2023-04-09T20:11:44.994723100Z][com.docker.diagnose.exe][I] (bc733f19) 00a63479-com.docker.diagnose C->S VMDockerdAPI GET /docker
[2023-04-09T20:11:44.995261200Z][com.docker.diagnose.exe][W] (bc733f19) 00a63479-com.docker.diagnose C<-S NoResponse GET /docker (538.1µs): Get "http://ipc/docker": open \\.\pipe\dockerLifecycleServer: The system cannot find the file specified.
[2023-04-09T20:11:44.995803600Z][com.docker.diagnose.exe][I] (bc733f19-1) 00a63479-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-04-09T20:11:44.996323100Z][com.docker.diagnose.exe][W] (bc733f19-1) 00a63479-com.docker.diagnose C<-S NoResponse GET /ping (519.5µs): Get "http://ipc/ping": open \\.\pipe\dockerLifecycleServer: The system cannot find the file specified.
[2023-04-09T20:11:45.997879300Z][com.docker.diagnose.exe][I] (bc733f19-2) 00a63479-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-04-09T20:11:45.998952100Z][com.docker.diagnose.exe][W] (bc733f19-2) 00a63479-com.docker.diagnose C<-S NoResponse GET /ping (1.3202ms): Get "http://ipc/ping": open \\.\pipe\dockerLifecycleServer: The system cannot find the file specified.
[2023-04-09T20:11:47.015458600Z][com.docker.diagnose.exe][I] (bc733f19-3) 00a63479-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-04-09T20:11:47.017355700Z][com.docker.diagnose.exe][W] (bc733f19-3) 00a63479-com.docker.diagnose C<-S NoResponse GET /ping (1.8972ms): Get "http://ipc/ping": open \\.\pipe\dockerLifecycleServer: The system cannot find the file specified.
[2023-04-09T20:11:48.028548400Z][com.docker.diagnose.exe][I] (bc733f19-4) 00a63479-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-04-09T20:11:48.029717200Z][com.docker.diagnose.exe][W] (bc733f19-4) 00a63479-com.docker.diagnose C<-S NoResponse GET /ping (1.1689ms): Get "http://ipc/ping": open \\.\pipe\dockerLifecycleServer: The system cannot find the file specified.
[2023-04-09T20:11:49.040477800Z][com.docker.diagnose.exe][I] (bc733f19-5) 00a63479-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-04-09T20:11:49.042006000Z][com.docker.diagnose.exe][W] (bc733f19-5) 00a63479-com.docker.diagnose C<-S NoResponse GET /ping (1.5282ms): Get "http://ipc/ping": open \\.\pipe\dockerLifecycleServer: The system cannot find the file specified.
[2023-04-09T20:11:50.049374500Z][com.docker.diagnose.exe][I] (bc733f19-6) 00a63479-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-04-09T20:11:50.050987500Z][com.docker.diagnose.exe][W] (bc733f19-6) 00a63479-com.docker.diagnose C<-S NoResponse GET /ping (1.073ms): Get "http://ipc/ping": open \\.\pipe\dockerLifecycleServer: The system cannot find the file specified.
[2023-04-09T20:11:51.052987300Z][com.docker.diagnose.exe][I] (bc733f19-7) 00a63479-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-04-09T20:11:51.053290600Z][com.docker.diagnose.exe][W] (bc733f19-7) 00a63479-com.docker.diagnose C<-S NoResponse GET /ping (303.3µs): Get "http://ipc/ping": open \\.\pipe\dockerLifecycleServer: The system cannot find the file specified.
[2023-04-09T20:11:52.063814400Z][com.docker.diagnose.exe][I] (bc733f19-8) 00a63479-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-04-09T20:11:52.063814400Z][com.docker.diagnose.exe][W] (bc733f19-8) 00a63479-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?
[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/09 14:12:03 error checking if default wsl distro is running: exit status 0xffffffff

Also this

 Invoke-WebRequest https://aka.ms/Debug-ContainerHost.ps1 -UseBasicParsing | Invoke-Expression            Checking for common problems                                                                                                         Container Host OS Product Name: Windows 10 Home                                                                                      Container Host OS Build Label: 22621.1.amd64fre.ni_release.220506-1250                                                               Describing Windows Version and Prerequisites                                                                                          [+] Is Windows 10 Anniversary Update or Windows Server 2016 950ms                                                                    [+] Has KB3192366, KB3194496, or later installed if running Windows build 14393 139ms                                                [+] Is not a build with blocking issues 27ms
 [-] Has 'Containers' feature installed 2.76s                                                                                           COMException: The requested operation requires elevation.                                                                            at <ScriptBlock>, <No file>: line 28                                                                                              Describing Docker is installed                                                                                                        [+] A Docker service is installed - 'Docker' or 'com.Docker.Service'  77ms                                                           [+] Service is running 29ms                                                                                                          [+] Docker.exe is in path 76.81s                                                                                                     [+] Docker is registered in the EventLog service 77ms                                                                               Describing User has permissions to use Docker daemon                                                                                  [+] docker.exe should not return access denied 79ms
Describing Windows container settings are correct
 [+] Do not have DisableVSmbOplock set to 1 38ms
 [+] Do not have zz values set 35ms
 [+] Do not have FDVDenyWriteAccess set to 1 24ms
Describing The right container base images are installed
error during connect: Get "http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.24/images/json": EOF
WARNING: No mcr.microsoft.com/* base images found. Checking for deprecated images.
 [-] At least one of 'mcr.microsoft.com/windows/servercore', 'mcr.microsoft.com/windows/nanoserver', 'mcr.microsoft.com/windows' or deprecated microsoft/windowsservercore, microsoft/nanoserver should be installed 37.46s
   ValidationMetadataException: The argument is null or empty. Provide an argument that is not null or empty, and then try the command again.
   ParameterBindingValidationException: Cannot validate argument on parameter 'Property'. The argument is null or empty. Provide an argument that is not null or empty, and then try the command again.
   at <ScriptBlock>, <No file>: line 126
Describing Container network is created
 [+] At least one local container network is available 38.38s
 [-] At least one NAT, Transparent, or L2Bridge Network exists 80ms
   Expected {0} to be greater than {0}
   218:       $totalnets | Should BeGreaterThan 0
   at <ScriptBlock>, <No file>: line 218
 [-] NAT Network's vSwitch is internal 52ms
   Expected: {Internal}
   But was:  {}
   223:       $switchType | Should Be "Internal"
   at <ScriptBlock>, <No file>: line 223
 [+] A Windows NAT is configured if a Docker NAT network exists 747ms
 [-] Specified Network Gateway IP for NAT network is assigned to Host vNIC 34ms
   Expected: value to not be empty
   237:       $natGatewayIP | Should Not BeNullOrEmpty
   at <ScriptBlock>, <No file>: line 237
 [-] NAT Network's internal prefix does not overlap with external IP' 35ms
   Expected {0} to be greater than {0}
   264:         $hostips.Count | Should BeGreaterThan 0
   at <ScriptBlock>, <No file>: line 264
Showing output from: docker info
Client:
 Context:    default
 Debug Mode: false
 Plugins:
  buildx: Docker Buildx (Docker Inc., v0.10.4)
  compose: Docker Compose (Docker Inc., v2.17.2)
  dev: Docker Dev Environments (Docker Inc., v0.1.0)
  extension: Manages Docker extensions (Docker Inc., v0.2.19)
  init: Creates Docker-related starter files for your project (Docker Inc., v0.1.0-beta.2)
  sbom: View the packaged-based Software Bill Of Materials (SBOM) for an image (Anchore Inc., 0.6.0)
  scan: Docker Scan (Docker Inc., v0.25.0)
  scout: Command line tool for Docker Scout (Docker Inc., v0.9.0)

Server:
ERROR: error during connect: Get "http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.24/info": EOF

Showing output from: docker version
Client:
 Cloud integration: v1.0.31
 Version:           20.10.24
 API version:       1.41
 Go version:        go1.19.7
 Git commit:        297e128
 Built:             Tue Apr  4 18:28:08 2023
 OS/Arch:           windows/amd64
 Context:           default
 Experimental:      true

Showing output from: docker network ls

Getting Warnings & errors in the Windows event logs from the last 24 hours
Logs saved to C:\Users\tyoc213\logs_20230409-141059.csv


Getting Docker for Windows daemon logs from the last execution
    Note: More logs may be available at C:\Users\tyoc213\AppData\Local\Docker. Only showing the latest 100 lines.

Steps to reproduce the behavior

docker run hello-world
docker: error during connect: Post "http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.24/containers/create": EOF.
See 'docker run --help'.

Wonder if there is something to do or it will never work??? (I have run some VMs with VBox on this computer)

[aignermax]

[EDIT] FOUND A Solution! -> Windows Update did the trick - simply install the newest huge accumulated update [/EDIT]

I am facing the same issues - Docker won't start even '

• after rebooting,
• reinstsalling,
• deleting all docker related files,
• pressing the "switch to windows containers" button or
• restarting the service,
• logging in using docker desktop

It always keeps saying

"Starting the Docker Engine...
Docker Engine is the underlying technology that runs containers"

I am using a

• Windows 11 Home
• Version 10.0.22621 Build 22621
• Lenovo Laptop with intel I7 12700H
• RTX 3070 GPU / Intel IRIS Xe Graphics
• WSL2

The old Docker worked fine for the last three months more or less stable (when you did the updates)
chatGPT did not find anything in the logs other than a volume that was not found:

"open /var/lib/docker/volumes: no such file or directory,"

Update:
After 5 Minutes or so I finally got an error Message:

System.Exception:
1 error occurred:
	* waiting for docker daemon: context deadline exceeded


   bei Docker.Engines.WSL2.LinuxWSL2Engine.<DoStartAsync>d__10.MoveNext() in C:\workspaces\PR-21378\src\github.com\docker\pinata\win\src\Docker.Engines\WSL2\LinuxWSL2Engine.cs:Zeile 93.
--- Ende der Stapelüberwachung vom vorhergehenden Ort, an dem die Ausnahme ausgelöst wurde ---
   bei System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   bei System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   bei Docker.ApiServices.StateMachines.TaskExtensions.<WrapAsyncInCancellationException>d__0.MoveNext() in C:\workspaces\PR-21378\src\github.com\docker\pinata\win\src\Docker.ApiServices\StateMachines\TaskExtensions.cs:Zeile 29.
--- Ende der Stapelüberwachung vom vorhergehenden Ort, an dem die Ausnahme ausgelöst wurde ---
   bei System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   bei System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   bei Docker.ApiServices.StateMachines.StartTransition.<DoRunAsync>d__7.MoveNext() in C:\workspaces\PR-21378\src\github.com\docker\pinata\win\src\Docker.ApiServices\StateMachines\StartTransition.cs:Zeile 79.
--- Ende der Stapelüberwachung vom vorhergehenden Ort, an dem die Ausnahme ausgelöst wurde ---
   bei System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   bei Docker.ApiServices.StateMachines.StartTransition.<DoRunAsync>d__7.MoveNext() in C:\workspaces\PR-21378\src\github.com\docker\pinata\win\src\Docker.ApiServices\StateMachines\StartTransition.cs:Zeile 108.
--- Ende der Stapelüberwachung vom vorhergehenden Ort, an dem die Ausnahme ausgelöst wurde ---
   bei System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   bei Docker.Engines.Engines.<WaitCurrentTransitionsAsync>d__30.MoveNext() in C:\workspaces\PR-21378\src\github.com\docker\pinata\win\src\Docker.Engines\Engines.cs:Zeile 282.
--- Ende der Stapelüberwachung vom vorhergehenden Ort, an dem die Ausnahme ausgelöst wurde ---
   bei System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   bei System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   bei Docker.Engines.Engines.<StartAsync>d__24.MoveNext() in C:\workspaces\PR-21378\src\github.com\docker\pinata\win\src\Docker.Engines\Engines.cs:Zeile 114.