Docker down "Unable to calculate image disk size"

[jpmc]

Description

I had been using Docker for two local projects, and suddenly they stopped working and when navigating to the UI I get "Unable to calculate image disk size" and everything seems to be offline.

I have no experimental features turned on, no addons from the marketplace, and I also disabled Resource Saver in advance when I updated this a while back since I saw the issues revolving around that as well. Though the issue sounds a lot like the Resource Saver issue anyway.

System is a 2021 M1 MacBook Pro running Monterey v12.7.5 (latest security update as of last week)

Reproduce

1. Have docker running.
2. Keep running, occasionally closing and reopening MacBook lid over time.
3. With no specific threshold, it will one day stop working.

Expected behavior

No response

docker version

Client:
 Cloud integration: v1.0.35+desktop.13
 Version:           26.1.1
 API version:       1.45
 Go version:        go1.21.9
 Git commit:        4cf5afa
 Built:             Tue Apr 30 11:44:56 2024
 OS/Arch:           darwin/arm64
 Context:           desktop-linux

docker info

Client:
 Version:    26.1.1
 Context:    desktop-linux
 Debug Mode: false
 Plugins:
  buildx: Docker Buildx (Docker Inc.)
    Version:  v0.14.0-desktop.1
    Path:     /Users/jcorrao/.docker/cli-plugins/docker-buildx
  compose: Docker Compose (Docker Inc.)
    Version:  v2.27.0-desktop.2
    Path:     /Users/jcorrao/.docker/cli-plugins/docker-compose
  debug: Get a shell into any image or container (Docker Inc.)
    Version:  0.0.29
    Path:     /Users/jcorrao/.docker/cli-plugins/docker-debug
  dev: Docker Dev Environments (Docker Inc.)
    Version:  v0.1.2
    Path:     /Users/jcorrao/.docker/cli-plugins/docker-dev
  extension: Manages Docker extensions (Docker Inc.)
    Version:  v0.2.23
    Path:     /Users/jcorrao/.docker/cli-plugins/docker-extension
  feedback: Provide feedback, right in your terminal! (Docker Inc.)
    Version:  v1.0.4
    Path:     /Users/jcorrao/.docker/cli-plugins/docker-feedback
  init: Creates Docker-related starter files for your project (Docker Inc.)
    Version:  v1.1.0
    Path:     /Users/jcorrao/.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:     /Users/jcorrao/.docker/cli-plugins/docker-sbom
  scout: Docker Scout (Docker Inc.)
    Version:  v1.8.0
    Path:     /Users/jcorrao/.docker/cli-plugins/docker-scout

Server:
ERROR: request returned Internal Server Error for API route and version http://%2FUsers%2Fjcorrao%2F.docker%2Frun%2Fdocker.sock/v1.45/info, check if the server supports the requested API version
errors pretty printing info

Diagnostics ID

2CE3EB5E-7411-490A-97F9-7A9A20E14C06/20240612203348

Additional Info

Output of com.docker.diagnose check for self-diagnostics.

Starting diagnostics

[2024-06-12T20:37:51.209331000Z][com.docker.diagnose.ipc] 01ce3503-diagnose -> <HOME>/Library/Containers/com.docker.docker/Data/backend.sock BackendAPI [2024-06-12T20:37:51.211115000Z][com.docker.diagnose.ipc] (fe948574) 01ce3503-diagnose C->S BackendAPI POST /idle/make-busy [2024-06-12T20:37:51.211973000Z][com.docker.diagnose.ipc] (fe948574) 01ce3503-diagnose C<-S a42233e8-BackendAPI POST /idle/make-busy (852.041µs): 0x1400071c4e0 [2024-06-12T20:37:52.212236000Z][com.docker.diagnose.ipc] (4f484481) 01ce3503-diagnose C->S BackendAPI GET /idle [2024-06-12T20:37:52.215050000Z][com.docker.diagnose.ipc] (4f484481) 01ce3503-diagnose C<-S a42233e8-BackendAPI GET /idle (2.782708ms): {"apisInFlight":{"/containers/json":1,"/images/json":1,"/v1.45/containers/json":2,"/volumes":1},"booted":true,"busyReason":["6 container(s)","in-flight APIs: map[/containers/json:1 /images/json:1 /v1.45/containers/json:2 /volumes:1]","timed activities: map[/idle/make-busy:28.997788125s]"],"containers":6,"idle":"bool","kubernetesEnabled":false,"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? [PASS] DD0018: does the host support virtualization? [PASS] DD0001: is the application running? [PASS] DD0017: can a VM be started? [PASS] DD0016: is the LinuxKit VM running? [FAIL] DD0004: is the Docker engine running? error during connect: Head "http://%2FUsers%2Fjcorrao%2FLibrary%2FContainers%2Fcom.docker.docker%2FData%2Fdocker.raw.sock/_ping": EOF [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] DD0038: is the connection to Docker working? prereq failed: is the Docker engine running? [FAIL] DD0014: are the backend processes running? com.docker.virtualization is not 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? [FAIL] DD0030: is the image access management authorized? prereq failed: is the Docker engine running? [PASS] DD0033: does the host have Internet access? [PASS] DD0018: does the host support virtualization? [PASS] DD0001: is the application running? [PASS] DD0017: can a VM be started? [PASS] DD0016: is the LinuxKit VM running? [WARN] DD0004: is the Docker engine running? error during connect: Head "http://%2FUsers%2Fjcorrao%2FLibrary%2FContainers%2Fcom.docker.docker%2FData%2Fdocker.raw.sock/_ping": EOF [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 3 warnings:

1 : The check: is the Docker engine running? Produced the following warning: error during connect: Head "http://%2FUsers%2Fjcorrao%2FLibrary%2FContainers%2Fcom.docker.docker%2FData%2Fdocker.raw.sock/_ping": EOF

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

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

3 : 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 the Docker engine running? Failed with: error during connect: Head "http://%2FUsers%2Fjcorrao%2FLibrary%2FContainers%2Fcom.docker.docker%2FData%2Fdocker.raw.sock/_ping": EOF

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

2 : The test: are the backend processes running? Failed with: com.docker.virtualization is not running

Not all of the backend processes are running.