search

docker / for-win

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

Docker Desktop not start #14203

Open abdelrazekrizk opened 4 months ago

abdelrazekrizk commented 4 months ago

Description

"connect ENOENT \\.\pipe\dockerDesktopBuildServer" diagnostics.log

Reproduce

start Docker Desktop

Expected behavior

just Enable Kubernetes yesterday and was ok

docker version

Docker Desktop 

4.32.0

docker info

no docker info

Diagnostics ID

3DA739DE-88C0-4D9A-8EB3-57F94AA5D435

Additional Info

PS C:\Users\Abdelrazek\Downloads\IBM Full-Stack JavaScript Developer Professional Certificate\10-Node.js & MongoDB Developing Back-end Database Applications> & "C:\Program Files\Docker\Docker\resources\com.docker.diagnose.exe" check Starting diagnostics

[2024-07-19T21:48:52.168475800Z][com.docker.diagnose.exe.ipc] 459f991c-diagnose -> \.\pipe\dockerBackendApiServer BackendAPI [2024-07-19T21:48:52.174782700Z][com.docker.diagnose.exe.ipc] (3fdd01d6) 459f991c-diagnose C->S BackendAPI POST /idle/make-busy [2024-07-19T21:48:52.176923800Z][com.docker.diagnose.exe.ipc] (3fdd01d6) 459f991c-diagnose C<-S 2dd54aa4-BackendAPI POST /idle/make-busy (2.1411ms): 0xc00040a690 [2024-07-19T21:48:53.175552700Z][com.docker.diagnose.exe.ipc] (d58237e2) 459f991c-diagnose C->S BackendAPI GET /idle [2024-07-19T21:48:53.177205000Z][com.docker.diagnose.exe.ipc] (d58237e2) 459f991c-diagnose C<-S 2dd54aa4-BackendAPI GET /idle (1.6523ms): {"apisInFlight":{"/_ping":2,"/v1.43/containers/json":1,"/v1.43/info":1,"/v1.43/version":1},"booted":false,"busyReason":["in-flight APIs: map[/_ping:2 /v1.43/containers/json:1 /v1.43/info:1 /v1.43/version:1]","timed activities: map[/idle/make-busy:28.9997519s]"],"containers":0,"idle":"bool","kubernetesEnabled":true,"reduced":false,"services":0,"timedActivities":{"/idle/make-busy":"float64"},"vmPaused":false,"vmRunning":true,"vmStopped":false,"windowsContainers":false}[PASS] DD0027: is there available disk space on the host? [PASS] DD0028: is there available VM disk space? [SKIP] DD0002: does the bootloader have virtualization enabled? [SKIP] DD0018: does the host support virtualization? [PASS] DD0001: is the application running? [SKIP] DD0022: is the Virtual Machine Platform Windows Feature enabled? [SKIP] 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? [FAIL] DD0029: is the WSL 2 Linux filesystem corrupt? listing block devices: : exit status 1 [PASS] DD0035: is the VM time synchronized? [FAIL] DD0017: can a VM be started? prereq failed: is the WSL 2 Linux filesystem corrupt? [FAIL] DD0016: is the LinuxKit VM running? prereq failed: can a VM be started? [FAIL] DD0004: is the Docker engine running? prereq failed: is the LinuxKit VM running? [PASS] DD0015: are the binary symlinks installed? [FAIL] DD0031: does the Docker API work? prereq failed: is the Docker engine running? [PASS] DD0013: is the $PATH ok? [FAIL] DD0003: is the Docker CLI working? prereq failed: is the Docker engine running? [FAIL] DD0005: is the user in the docker-users group? prereq failed: is the LinuxKit VM running? [FAIL] DD0038: is the connection to Docker working? prereq failed: is the Docker engine running? [FAIL] DD0014: are the backend processes running? prereq failed: is the LinuxKit VM running? [FAIL] DD0007: is the backend responding? prereq failed: are the backend processes running? [FAIL] DD0009: is the vpnkit API responding? prereq failed: are the backend processes running? [FAIL] DD0010: is the Docker API proxy responding? prereq failed: are the backend processes running? [SKIP] DD0006: is the Docker Desktop Service responding? [FAIL] DD0030: is the image access management authorized? prereq failed: is the Docker engine running? [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?
[WARN] DD0029: is the WSL 2 Linux filesystem corrupt? listing block devices: : exit status 1 [PASS] DD0035: is the VM time synchronized? [WARN] DD0017: can a VM be started? prereq failed: is the WSL 2 Linux filesystem corrupt? [WARN] DD0016: is the LinuxKit VM running? prereq failed: can a VM be started? [WARN] DD0004: is the Docker engine running? prereq failed: is the LinuxKit VM running? [PASS] DD0015: are the binary symlinks installed? [WARN] DD0031: does the Docker API work? prereq failed: is the Docker engine running? [WARN] DD0032: do Docker networks overlap with host IPs? prereq failed: does the Docker API work?

   Please note the following 6 warnings:

                                        1 : The check: is the WSL 2 Linux filesystem corrupt?
                                                                                                 Produced the following warning: listing block devices: : exit status 1

                                                                                                                                                                       If the WSL 2 Linux filesystem is corrupt then Docker Desktop cannot start.
                                      There is a known issue fixed in Windows Insider builds which can cause filesystem corruption, see:
                                                                                                                                        https://github.com/microsoft/WSL/issues/5895 .

                                                                                                                                                                                      Try running "wsl

--shutdown" to stop your WSL Virtual Machine. When it restarts it will run a filesystem check and hopefully fix the problem.

                                                                                                                       2 : The check: can a VM be started?
                                                                                                                                                              Produced the following warning: prereq failed: is the WSL 2 Linux filesystem corrupt?

                                        The Docker engine runs inside a Linux VM. Therefore we must be able to start Virtual Machines.

                                                                                                                                      3 : The check: is the LinuxKit VM running?
                                                                                                                                                                                    Produced the following warning: prereq failed: can a VM be started?

                                            The Docker engine runs inside a Linux VM. Therefore the VM must be running.

                                                                                                                       4 : The check: is the Docker engine running?
                                                                                                                                                                       Produced the following warning:

prereq failed: is the LinuxKit VM running?

                                      The Docker engine manages all containers and images on the host. Check the dockerd.log to see why it failed to start.

                                                                                                                                                           5 : The check: does the Docker API work?

Produced the following warning: prereq failed: is the Docker engine running?

                                                                        If the Docker API is not available from the host then Docker Desktop will not work correctly.

                                                                                                                                                                     6 : The check: do Docker networks

overlap with host IPs? Produced the following warning: prereq failed: does the Docker API work?

                                                                                              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 1 issue:

                                                1 : The test: is the WSL 2 Linux filesystem corrupt?
                                                                                                        Failed with: listing block devices: : exit status 1

                                                                                                                                                           If the WSL 2 Linux filesystem is corrupt then Docker Desktop cannot start.
                          There is a known issue fixed in Windows Insider builds which can cause filesystem corruption, see:
                                                                                                                            https://github.com/microsoft/WSL/issues/5895 .

                                                                                                                                                                          Try running "wsl --shutdown"

to stop your WSL Virtual Machine. When it restarts it will run a filesystem check and hopefully fix the problem.

PS C:\Users\Abdelrazek\Downloads\IBM Full-Stack JavaScript Developer Professional Certificate\10-Node.js & MongoDB Developing Back-end Database Applications> wsl --shutdown PS C:\Users\Abdelrazek\Downloads\IBM Full-Stack JavaScript Developer Professional Certificate\10-Node.js & MongoDB Developing Back-end Database Applications> wsl To run a command as administrator (user "root"), use "sudo ". See "man sudo_root" for details.

dev@Workstation:/mnt/c/Users/Abdelrazek/Downloads/IBM Full-Stack JavaScript Developer Professional Certificate/10-Node.js & MongoDB Developing Back-end Database Applications$ 20240719213716.zip

abdelrazekrizk commented 4 months ago

after I close the app and restart it docker version give me that output now it work C:\Users\Abdelrazek\Downloads\IBM Full-Stack JavaScript Developer Professional Certificate\10-Node.js & MongoDB Developing Back-end Database Applications>docker version Client: Version: 27.0.3 API version: 1.46 Go version: go1.21.11 Git commit: 7d4bcd8 Built: Sat Jun 29 00:03:32 2024 OS/Arch: windows/amd64 Context: desktop-linux error during connect: Get "http://%2F%2F.%2Fpipe%2FdockerDesktopLinuxEngine/v1.46/version": EOF

Sachi9892 commented 4 months ago

Delete the .docker file and then restart docker desktop . you can find the .docker file mostly at C:/Yourname/