Docker Desktop reports incorrect VM Disk usage, possibly causing Engine to be unable to start

[theokrammer]

Description

The VM disk usage reported in Docker Desktop (180 GB) is way bigger than what docker system df reports (~30GB).

This causes error in containers complaining about not enough space on disk, e.g. nginx: 2023/06/01 14:19:09 [alert] 29#29: *44 write() to "/etc/nginx/stdout" failed (28: No space left on device) while logging request, client: 172.20.0.9, server: localhost, request: "GET /feed HTTP/1.1", upstream: "fastcgi://unix:/run/php/php8.1-fpm.sock", host: "front.bnn.local" Unrecognized input header: 99

After a restart the engine is no longer able to start, no matter if using experimental features or not.

Reproduce

No guarantee that this can reproduce it, i hope the diagnostics are of help. After a reinstall i simply have to work with it a few weeks until i have to increase the VM size.

Expected behavior

Docker Desktop should be able to start the engine when enough space is available, and it should not use over 150GB overhead if the images, build cache etc. only need < 30 GB. Additionally, the space the VM requires should not increase as quickly as it does.

docker version

Error response from daemon: Bad response from Docker engine
Client:
 Cloud integration: v1.0.31
 Version:           23.0.5
 API version:       1.42
 Go version:        go1.19.8
 Git commit:        bc4487a
 Built:             Wed Apr 26 16:12:52 2023
 OS/Arch:           darwin/amd64
 Context:           desktop-linux

docker info

Client:
 Context:    desktop-linux
 Debug Mode: false
 Plugins:
  buildx: Docker Buildx (Docker Inc.)
    Version:  v0.10.4
    Path:     /Users/theojunge/.docker/cli-plugins/docker-buildx
  compose: Docker Compose (Docker Inc.)
    Version:  v2.17.3
    Path:     /Users/theojunge/.docker/cli-plugins/docker-compose
  dev: Docker Dev Environments (Docker Inc.)
    Version:  v0.1.0
    Path:     /Users/theojunge/.docker/cli-plugins/docker-dev
  extension: Manages Docker extensions (Docker Inc.)
    Version:  v0.2.19
    Path:     /Users/theojunge/.docker/cli-plugins/docker-extension
  init: Creates Docker-related starter files for your project (Docker Inc.)
    Version:  v0.1.0-beta.4
    Path:     /Users/theojunge/.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/theojunge/.docker/cli-plugins/docker-sbom
  scan: Docker Scan (Docker Inc.)
    Version:  v0.26.0
    Path:     /Users/theojunge/.docker/cli-plugins/docker-scan
  scout: Command line tool for Docker Scout (Docker Inc.)
    Version:  v0.10.0
    Path:     /Users/theojunge/.docker/cli-plugins/docker-scout

Server:
ERROR: Error response from daemon: Bad response from Docker engine
errors pretty printing info

Diagnostics ID

76B67562-1517-4F48-930A-3529B3B62A83/20230602074017

Additional Info

I had this issue a few times already, but was not able to capture anything, but could only solve it temporarily by increasing the amount of disk space docker is able to use.

I am appending the diagnostics output from when the App had ~30GB left of the 180GB, even though docker system df did not report anything different, as i have not really downloaded or built new images in that time. This was about 1 week ago, so the size this VM uses increases very quickly. docker logs 25.05.2023- 36.22 free of 183.zip