for-win icon indicating copy to clipboard operation
for-win copied to clipboard

"Starting the Docker Engine..." hangs

Open fabpico opened this issue 2 years ago • 5 comments

Description

After system upgrade to Windows 11, Docker Desktop v4.18.0 was not able anymore to upgrade itself, and Docker Desktop shutdown was also not possible anymore.
So I uninstalled it, and installed the latest version (currently v4.20.1). And it hangs on startup.

First, from https://stackoverflow.com/questions/71238673/docker-desktop-starting-forever-on-windows I tried wsl --update. It updated something, but after PC reboot, Docker Desktop still hangs on startup.

Then from https://stackoverflow.com/questions/43041331/docker-forever-in-docker-is-starting-at-windows-task I tried

wsl --unregister docker-desktop
wsl --unregister docker-desktop-data

in Powershell. It did something, but still after PC reboot, Docker Desktop hangs on startup.

Reproduce

  1. Install latest version (currently v4.20.1) on Windows 11
  2. Start Docker Desktop

Expected behavior

Start should succeed.

docker version

error during connect: this error may indicate that the docker daemon is not running: Get "http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.24/version": open //./pipe/docker_engine: The system cannot find the file specified.
Client:
 Cloud integration: v1.0.33
 Version:           24.0.2
 API version:       1.43
 Go version:        go1.20.4
 Git commit:        cb74dfc
 Built:             Thu May 25 21:53:15 2023
 OS/Arch:           windows/amd64
 Context:           default

docker info

Client:
 Version:    24.0.2
 Context:    default
 Debug Mode: false
 Plugins:
  buildx: Docker Buildx (Docker Inc.)
    Version:  v0.10.5
    Path:     C:\Program Files\Docker\cli-plugins\docker-buildx.exe
  compose: Docker Compose (Docker Inc.)
    Version:  v2.18.1
    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.19
    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.4
    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: Command line tool for Docker Scout (Docker Inc.)
    Version:  v0.12.0
    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

B5BDD68C-0B91-4813-A482-B64F2C4A48E2/20230607132030

Additional Info

No response

fabpico avatar Jun 07 '23 13:06 fabpico

Fixed by deleting settings.json. https://stackoverflow.com/questions/71089617/docker-not-starting-on-windows-11-with-wsl-2

fabpico avatar Jun 08 '23 07:06 fabpico

I reopen because deleting settings.json is a workaround. It should just work without that workaround.

fabpico avatar Jun 13 '23 06:06 fabpico

Unfortunately deleting the settings.json didn't fix the stuck loading screen on my pc after upgrading to version 4.20.1

grosssmutttr avatar Jun 16 '23 14:06 grosssmutttr

Yeah, there's something up with this version or the update recently pushed...

Had to reboot Windows, at which time I noticed Docker Engine wasn't registering in Docker Desktop as actually starting...

error during connect: this error may indicate that the docker daemon is not running: Get "http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.24/version": open //./pipe/docker_engine: The system cannot find the file specified.
Client:
 Cloud integration: v1.0.33
 Version:           24.0.2
 API version:       1.43
 Go version:        go1.20.4
 Git commit:        cb74dfc
 Built:             Thu May 25 21:53:15 2023
 OS/Arch:           windows/amd64
 Context:           default

Followed the SO thread and renamed settings.json - at which time I restarted Docker Desktop and it automatically started installing 4.21.1...

Post installation:

> docker version
Client:
 Cloud integration: v1.0.35
 Version:           24.0.2
 API version:       1.43
 Go version:        go1.20.4
 Git commit:        cb74dfc
 Built:             Thu May 25 21:53:15 2023
 OS/Arch:           windows/amd64
 Context:           default

Server: Docker Desktop 4.21.1 (114176)
 Engine:
  Version:          24.0.2
  API version:      1.43 (minimum version 1.12)
  Go version:       go1.20.4
  Git commit:       659604f
  Built:            Thu May 25 21:52:17 2023
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.6.21
  GitCommit:        3dce8eb055cbb6872793272b4f20ed16117344f8
 runc:
  Version:          1.1.7
  GitCommit:        v1.1.7-0-g860f061
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

Once Docker Engine started and I was able to access Docker Desktop, I see that 4.22.0 (117440) is available as an update.

I was able to successfully install 4.22.0 as an upgrade through Docker Desktop:

docker version Client: Cloud integration: v1.0.35-desktop+001 Version: 24.0.5 API version: 1.43 Go version: go1.20.6 Git commit: ced0996 Built: Fri Jul 21 20:36:24 2023 OS/Arch: windows/amd64 Context: default

Server: Docker Desktop 4.22.0 (117440) Engine: Version: 24.0.5 API version: 1.43 (minimum version 1.12) Go version: go1.20.6 Git commit: a61e2b4 Built: Fri Jul 21 20:35:45 2023 OS/Arch: linux/amd64 Experimental: false containerd: Version: 1.6.21 GitCommit: 3dce8eb055cbb6872793272b4f20ed16117344f8 runc: Version: 1.1.7 GitCommit: v1.1.7-0-g860f061 docker-init: Version: 0.19.0 GitCommit: de40ad0

mattezell avatar Aug 08 '23 16:08 mattezell

Got the same problem few days ago. After hours of researching, found that the problem was in Virtual disk limit. Enlarged it in settings.json and docker started successfully. Interesting thing was that only downgrading from latest to docket version 4.26.1 showed me error with message about disk space.

LordScoutTG avatar Aug 31 '24 05:08 LordScoutTG