Stuck on "Starting the Docker Engine..."

[groovecoder]

Description

Docker is stuck on "Starting the Docker Engine..."

Reproduce

Mac OS Monterey 12.7.6 (21H1320) Docker v4.38.0

1. Open Docker.app

Expected behavior

Docker opens and runs successfully

docker version

Client:
 Version:           27.5.1
 API version:       1.47
 Go version:        go1.22.11
 Git commit:        9f9e405
 Built:             Wed Jan 22 13:37:19 2025
 OS/Arch:           darwin/arm64
 Context:           desktop-linux


request returned Internal Server Error for API route and version http://{redacted}.docker%2Frun%2Fdocker.sock/v1.47/version, check if the server supports the requested API version

docker info

Client:
 Version:    27.5.1
 Context:    desktop-linux
 Debug Mode: false
 Plugins:
  ai: Ask Gordon - Docker Agent (Docker Inc.)
    Version:  v0.7.3
    Path:     {home-dir}/.docker/cli-plugins/docker-ai
  buildx: Docker Buildx (Docker Inc.)
    Version:  v0.20.1-desktop.2
    Path:     {home-dir}/.docker/cli-plugins/docker-buildx
  compose: Docker Compose (Docker Inc.)
    Version:  v2.32.4-desktop.1
    Path:     {home-dir}/.docker/cli-plugins/docker-compose
  debug: Get a shell into any image or container (Docker Inc.)
    Version:  0.0.38
    Path:     {home-dir}/.docker/cli-plugins/docker-debug
  desktop: Docker Desktop commands (Beta) (Docker Inc.)
    Version:  v0.1.4
    Path:     {home-dir}/.docker/cli-plugins/docker-desktop
  dev: Docker Dev Environments (Docker Inc.)
    Version:  v0.1.2
    Path:     {home-dir}/.docker/cli-plugins/docker-dev
  extension: Manages Docker extensions (Docker Inc.)
    Version:  v0.2.27
    Path:     {home-dir}/.docker/cli-plugins/docker-extension
  feedback: Provide feedback, right in your terminal! (Docker Inc.)
    Version:  v1.0.5
    Path:     {home-dir}/.docker/cli-plugins/docker-feedback
  init: Creates Docker-related starter files for your project (Docker Inc.)
    Version:  v1.4.0
    Path:     {home-dir}/.docker/cli-plugins/docker-init
  sbom: View the packaged-based Software Bill Of Materials (SBOM) for an image (Anchore Inc.)
    Version:  0.6.0
    Path:     {home-dir}/.docker/cli-plugins/docker-sbom
  scout: Docker Scout (Docker Inc.)
    Version:  v1.16.1
    Path:     {home-dir}/.docker/cli-plugins/docker-scout

Server:
ERROR: request returned Internal Server Error for API route and version http://{home-dir}%2F.docker%2Frun%2Fdocker.sock/v1.47/info, check if the server supports the requested API version
errors pretty printing info

Diagnostics ID

1C4F2166-92D7-47F2-A6C8-8D2522F5E374/20250224232648 or dfk095yn0jv2cvz3d825tsm80000gn

Additional Info

1. Restarting Docker doesn't fix
2. Restarting Mac OS doesn't fix
3. Restore to Factory Settings doesn't fix
4. Re-installing Docker doesn't fix

[ByteSecurity]

4.29.0 I also ran into this problem but managed to resolve it by switching to version 4.29. https://desktop.docker.com/mac/main/arm64/145265/Docker.dmg

[groovecoder]

4.29.0 works.

[jpbriend]

Hi @groovecoder , the diagnostic was not uploaded. Can you check if you have any network limitation which would prevent uploading it? Reminder: you can run the diagnostic via the commandline: https://docs.docker.com/desktop/troubleshoot-and-support/troubleshoot/#diagnose-from-the-terminal. Don't forget the gather -upload parameter at the end.

[groovecoder]

I tried the gather -upload from the command-line at first. It definitely seems like a networking issue where docker can't access the network. So is there another way I can manually upload the diagnostics data somewhere secure?

(Though to be honest, I've downgraded back to 4.29.0 to fix the issue.

[jpbriend]

If you are a customer and have access to our Support, you can create a ticket, they probably have a way for you to provide the diagnostic in it.

[arvera]

I am having the same problem here, My docker was working fine now I am dead in the water.

Diagnostic uploaded under id: F1125B82-0093-4AF7-87B1-D31CA7991158/20250227220511

[jpbriend]

Hi @arvera , in your case, Docker daemon can not start because there is no space available:

failed to start daemon: failed to get temp dir to generate runtime scripts: mkdir /var/lib/docker/gen-runtimes1830943291: no space left on device

Try to increase the size of the disk allocated to the VM, restart Docker Desktop, then when you can successfully run docker commands, prune some old data. It's important to regularly remove unused data, such as unused layers from the disk.

[tigerquoll]

Docker hangs on engine startup for me as well: 7CEC80B0-3DAE-4F80-B6E4-B6A1F97C8443/20250304221533

[jpbriend]

Hey @tigerquoll , you have the same issue: no space disk left. Apply the same recommendation as above and don't forget to regularly clean up things in Docker.

[Amokers]

I faced same issue with debian 12 (v4.38.0), resolve it by switching to version 4.29