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

After installing docker 4.24 in windows its not getting started with below error. #13731

Open Gomathivignesh opened 1 year ago

Gomathivignesh commented 1 year ago

Description

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? [SKIP] DD0002: does the bootloader have virtualization enabled? [SKIP] DD0018: does the host support virtualization? [FAIL] DD0001: is the application running? Docker is not running [SKIP] DD0022: is the Virtual Machine Platform Windows Feature enabled? [SKIP] DD0021: is the WSL 2 Windows Feature enabled? [FAIL] DD0024: is WSL installed? exit status 0xfffffe44 [FAIL] DD0025: are WSL distros installed? prereq failed: is WSL installed? [PASS] DD0026: is the WSL LxssManager service running? [FAIL] DD0029: is the WSL 2 Linux filesystem corrupt? prereq failed: are WSL distros installed? [FAIL] DD0035: is the VM time synchronized? prereq failed: is WSL installed? [FAIL] DD0017: can a VM be started? prereq failed: is WSL installed? [FAIL] DD0016: is the LinuxKit VM running? prereq failed: is the application running? [FAIL] DD0011: are the LinuxKit services running? prereq failed: is the LinuxKit VM running? [FAIL] DD0004: is the Docker engine running? prereq failed: are the LinuxKit services 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] DD0008: is the native API responding? prereq failed: is the application 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? [WARN] DD0001: is the application running? Docker is not running [PASS] DD0022: is the Virtual Machine Platform Windows Feature enabled? [PASS] DD0021: is the WSL 2 Windows Feature enabled? [WARN] DD0024: is WSL installed? exit status 0xfffffe44 [WARN] DD0025: are WSL distros installed? prereq failed: is WSL installed? [PASS] DD0026: is the WSL LxssManager service running? [WARN] DD0029: is the WSL 2 Linux filesystem corrupt? prereq failed: are WSL distros installed? [WARN] DD0035: is the VM time synchronized? prereq failed: is WSL installed? [WARN] DD0017: can a VM be started? prereq failed: is WSL installed? [WARN] DD0016: is the LinuxKit VM running? prereq failed: is the application running? [WARN] DD0011: are the LinuxKit services running? prereq failed: is the LinuxKit VM running? [WARN] DD0004: is the Docker engine running? prereq failed: are the LinuxKit services 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 17 warnings:

1 : The check: is the application running? Produced the following warning: Docker is not running

Is the Docker Desktop application running?

2 : The check: is WSL installed? Produced the following warning: exit status 0xfffffe44

The Docker engine runs inside a WSL environment. Therefore WSL must be installed. Try running wsl --status.

3 : The check: is WSL installed? Produced the following warning: exit status 0xfffffe44

The Docker engine runs inside a WSL environment. Therefore WSL must be installed. Try running wsl --status.

4 : The check: are WSL distros installed? Produced the following warning: prereq failed: is WSL installed?

The Docker engine uses several WSL distributions. Therefore these must be installed.

5 : The check: is WSL installed? Produced the following warning: exit status 0xfffffe44

The Docker engine runs inside a WSL environment. Therefore WSL must be installed. Try running wsl --status.

6 : The check: are WSL distros installed? Produced the following warning: prereq failed: is WSL installed?

The Docker engine uses several WSL distributions. Therefore these must be installed.

7 : The check: is the WSL 2 Linux filesystem corrupt? Produced the following warning: prereq failed: are WSL distros installed?

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.

8 : The check: is WSL installed? Produced the following warning: exit status 0xfffffe44

The Docker engine runs inside a WSL environment. Therefore WSL must be installed. Try running wsl --status.

9 : The check: is WSL installed? Produced the following warning: exit status 0xfffffe44

The Docker engine runs inside a WSL environment. Therefore WSL must be installed. Try running wsl --status.

10 : The check: are WSL distros installed? Produced the following warning: prereq failed: is WSL installed?

The Docker engine uses several WSL distributions. Therefore these must be installed.

11 : The check: is the VM time synchronized? Produced the following warning: prereq failed: is WSL installed?

The VM time must be in sync with the host, otherwise Docker Desktop will not work correctly.

Ensure you are using a modern WSL 2 kernel (see "wsl --update"). If this problem persists, try manually synchronizing the VM clock with "sudo hwclock -s".

12 : The check: can a VM be started? Produced the following warning: prereq failed: is WSL installed?

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

13 : The check: is the LinuxKit VM running? Produced the following warning: prereq failed: is the application running?

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

14 : The check: are the LinuxKit services running? Produced the following warning: prereq failed: is the LinuxKit VM running?

The Docker engine runs inside a Linux VM as a service. Therefore the services must have started.

15 : The check: is the Docker engine running? Produced the following warning: prereq failed: are the LinuxKit services running?

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

16 : 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.

17 : 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 2 issues:

1 : The test: is WSL installed? Failed with: exit status 0xfffffe44

The Docker engine runs inside a WSL environment. Therefore WSL must be installed. Try running wsl --status.

2 : The test: is the application running? Failed with: Docker is not running

Is the Docker Desktop application running?

Reproduce

starting docker desktop

Expected behavior

No response

docker version

4.24

docker info

Client:
 Version:    24.0.6
 Context:    default
 Debug Mode: false
 Plugins:
  buildx: Docker Buildx (Docker Inc.)
    Version:  v0.11.2-desktop.5
    Path:     C:\Program Files\Docker\cli-plugins\docker-buildx.exe
  compose: Docker Compose (Docker Inc.)
    Version:  v2.22.0-desktop.2
    Path:     C:\Program Files\Docker\cli-plugins\docker-compose.exe
  dev: Docker Dev Environments (Docker Inc.)
    Version:  v0.1.0
    Path:     C:\Program Files\Docker\cli-plugins\docker-dev.exe
  extension: Manages Docker extensions (Docker Inc.)
    Version:  v0.2.20
    Path:     C:\Program Files\Docker\cli-plugins\docker-extension.exe
  init: Creates Docker-related starter files for your project (Docker Inc.)
    Version:  v0.1.0-beta.8
    Path:     C:\Program Files\Docker\cli-plugins\docker-init.exe
  sbom: View the packaged-based Software Bill Of Materials (SBOM) for an image (Anchore Inc.)
    Version:  0.6.0
    Path:     C:\Program Files\Docker\cli-plugins\docker-sbom.exe
  scan: Docker Scan (Docker Inc.)
    Version:  v0.26.0
    Path:     C:\Program Files\Docker\cli-plugins\docker-scan.exe
  scout: Docker Scout (Docker Inc.)
    Version:  v1.0.7
    Path:     C:\Program Files\Docker\cli-plugins\docker-scout.exe

Server:
ERROR: error during connect: this error may indicate that the docker daemon is not running: Get "http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.24/info": open //./pipe/docker_engine: The system cannot find the file specified.
errors pretty printing info

Diagnostics ID

A2D60848-61DA-4C70-8B73-B2224E2565E3/20231010000016

Additional Info

No response

leogregianin commented 1 year ago

Same problem here. All crashed

felipemeres commented 1 year ago

Same here

HollisTech commented 12 months ago

Totally busted for me too. I uninstalled 4.24.1 and downloaded and installed 4.24.0, and so far 4.24.0 is working for me.

sr5155 commented 12 months ago

@HollisTech How to download 4.24.0.

HollisTech commented 12 months ago

https://docs.docker.com/desktop/release-notes/ has links to recent releases.

leogregianin commented 12 months ago

Update to 4.24.2 version and another problem:

[Window Title]
Docker Desktop

[Main Instruction]
Something went wrong

[Content]
Starting services: initializating Docker API Proxy: open \\.\pipe\docker_engine: Access Denied.

[Quit] [Diagnose & Feedback] [Reset Docker to factory defaults]
bsousaa commented 11 months ago

what's the output of wsl --status?

leogregianin commented 11 months ago

what's the output of wsl --status?

PS C:\Users\leo> wsl --status
Distribuição Padrão: Debian
Versão Padrão: 2
dpgindler commented 11 months ago

Same here.... ;-(

bsousaa commented 11 months ago

@dpgindler @leogregianin can you share a diagnostics id? You can generate one from the terminal. See https://docs.docker.com/desktop/troubleshoot/overview/#diagnose-from-the-terminal

dpgindler commented 11 months ago

Sorry.. @bsousaa I tried several things and just nuked it..

leogregianin commented 11 months ago

@dpgindler @leogregianin can you share a diagnostics id? You can generate one from the terminal. See https://docs.docker.com/desktop/troubleshoot/overview/#diagnose-from-the-terminal

[2023-10-18T17:15:08.607244400Z][com.docker.diagnose.exe][I] Uploaded diagnostics to: https://docker-pinata-support.s3.amazonaws.com/incoming/3/B3EA5DB6-1D24-4BE5-BA03-8EBD6C149778/20231018171135.zip

Diagnostics ID: B3EA5DB6-1D24-4BE5-BA03-8EBD6C149778/20231018171135 (uploaded)

danisherror commented 11 months ago

you can follow the solution given in https://github.com/docker/for-win/issues/12548

Some other things, if you are using Windows,check that virtualization is enabled { you can check this by going to task manager to performance, there you can see the virtualization is enabled or not,}

After following steps the step in https://github.com/docker/for-win/issues/12548 issue and enabling the virtualization in my computer it worked.

cforce commented 11 months ago

Same here

av1v3k commented 8 months ago

I had uninstalled Docker Desktop post reading those comments above.