You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running docker compose up --build with memory already scarce (due to other tasks in the background), the command can sometimes error out with a message like the following: failed to solve: Internal: error committing gdrdsp9bnystssa2etb51tjfl: write /var/lib/buildkit/runc-overlayfs/metadata_v2.db: input/output error.
After shutting down memory-intensive tasks in the background, running docker compose up --build again produces the following error:
unable to get image '<local_image_being_built>': Error response from daemon: failed to get config descriptor: rpc error: code = Unknown desc = blob sha256:dca1980b348c21e5a7c06e90516249201760aff5e718d03ca940f6a00c33d1da expected at /var/lib/desktop-containerd/daemon/io.containerd.content.v1.content/blobs/sha256/dca1980b348c21e5a7c06e90516249201760aff5e718d03ca940f6a00c33d1da: open /var/lib/desktop-containerd/daemon/io.containerd.content.v1.content/blobs/sha256/dca1980b348c21e5a7c06e90516249201760aff5e718d03ca940f6a00c33d1da: input/output error
Running docker image ls produces something similar:
Error response from daemon: rpc error: code = Unknown desc = blob sha256:5781759b3d27734d4d548fcbaf60b1180dbf4290e708f01f292faa6ae764c5e6 expected at /var/lib/desktop-containerd/daemon/io.containerd.content.v1.content/blobs/sha256/5781759b3d27734d4d548fcbaf60b1180dbf4290e708f01f292faa6ae764c5e6: open /var/lib/desktop-containerd/daemon/io.containerd.content.v1.content/blobs/sha256/5781759b3d27734d4d548fcbaf60b1180dbf4290e708f01f292faa6ae764c5e6: input/output error
Further running docker system prune -a results in:
Error response from daemon: 26 errors occurred: * rpc error: code = Unknown desc = blob sha256:bf8503f739ee445559e7cc9c324fd7dd9d9c10f10b10f04fb5f2de5741d4a2c1 expected at /var/lib/desktop-containerd/daemon/io.containerd.content.v1.content/blobs/sha256/bf8503f739ee445559e7cc9c324fd7dd9d9c10f10b10f04fb5f2de5741d4a2c1: open /var/lib/desktop-containerd/daemon/io.containerd.content.v1.content/blobs/sha256/bf8503f739ee445559e7cc9c324fd7dd9d9c10f10b10f04fb5f2de5741d4a2c1: input/output error ...
Steps To Reproduce
I'm running a Macbook Pro (M1) and Sequoia 15.2 OS.
Config-wise, I have a docker compose file that is building a local Dockerfile.
I'm running docker compose up --build
I'm getting rpc error: code = Unknown desc = blob ... with a set of file paths that don't exist on my machine.
Compose Version
Docker Compose version v2.32.4-desktop.1
Docker Environment
Client:
Version: 27.5.1
Context: desktop-linux
Debug Mode: false
Plugins:
ai: Ask Gordon - Docker Agent (Docker Inc.)
Version: v0.7.3
Path: /Users/daviddoyle/.docker/cli-plugins/docker-ai
buildx: Docker Buildx (Docker Inc.)
Version: v0.20.1-desktop.2
Path: /Users/daviddoyle/.docker/cli-plugins/docker-buildx
compose: Docker Compose (Docker Inc.)
Version: v2.32.4-desktop.1
Path: /Users/daviddoyle/.docker/cli-plugins/docker-compose
debug: Get a shell into any image or container (Docker Inc.)
Version: 0.0.38
Path: /Users/daviddoyle/.docker/cli-plugins/docker-debug
desktop: Docker Desktop commands (Beta) (Docker Inc.)
Version: v0.1.4
Path: /Users/daviddoyle/.docker/cli-plugins/docker-desktop
dev: Docker Dev Environments (Docker Inc.)
Version: v0.1.2
Path: /Users/daviddoyle/.docker/cli-plugins/docker-dev
extension: Manages Docker extensions (Docker Inc.)
Version: v0.2.27
Path: /Users/daviddoyle/.docker/cli-plugins/docker-extension
feedback: Provide feedback, right in your terminal! (Docker Inc.)
Version: v1.0.5
Path: /Users/daviddoyle/.docker/cli-plugins/docker-feedback
init: Creates Docker-related starter files for your project (Docker Inc.)
Version: v1.4.0
Path: /Users/daviddoyle/.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/daviddoyle/.docker/cli-plugins/docker-sbom
scout: Docker Scout (Docker Inc.)
Version: v1.16.1
Path: /Users/daviddoyle/.docker/cli-plugins/docker-scout
Server:
Containers: 15
Running: 12
Paused: 0
Stopped: 3
Images: 20
Server Version: 27.5.1
Storage Driver: overlayfs
driver-type: io.containerd.snapshotter.v1
Logging Driver: json-file
Cgroup Driver: cgroupfs
Cgroup Version: 2
Plugins:
Volume: local
Network: bridge host ipvlan macvlan null overlay
Log: awslogs fluentd gcplogs gelf journald json-file local splunk syslog
CDI spec directories:
/etc/cdi
/var/run/cdi
Swarm: inactive
Runtimes: io.containerd.runc.v2 runc
Default Runtime: runc
Init Binary: docker-init
containerd version: bcc810d6b9066471b0b6fa75f557a15a1cbf31bb
runc version: v1.1.12-0-g51d5e946
init version: de40ad0
Security Options:
seccomp
Profile: unconfined
cgroupns
Kernel Version: 6.12.5-linuxkit
Operating System: Docker Desktop
OSType: linux
Architecture: aarch64
CPUs: 8
Total Memory: 11.67GiB
Name: docker-desktop
ID: 001fb9cf-2225-4a76-bf86-944ea9d1e800
Docker Root Dir: /var/lib/docker
Debug Mode: true
File Descriptors: 67
Goroutines: 104
System Time: 2025-03-07T14:09:04.891858304Z
EventsListeners: 18
HTTP Proxy: http.docker.internal:3128
HTTPS Proxy: http.docker.internal:3128
No Proxy: hubproxy.docker.internal
Labels:
com.docker.desktop.address=unix:///Users/daviddoyle/Library/Containers/com.docker.docker/Data/docker-cli.sock
Experimental: false
Insecure Registries:
hubproxy.docker.internal:5555
127.0.0.0/8
Live Restore Enabled: false
WARNING: daemon is not using the default seccomp profile
Anything else?
The text was updated successfully, but these errors were encountered:
AFAICT this issue is not specific to docker compose, and is actually related to buildkit and/or containerd integration in docker engine. You should report this to https://github.com/moby/moby
Description
When running
docker compose up --build
with memory already scarce (due to other tasks in the background), the command can sometimes error out with a message like the following:failed to solve: Internal: error committing gdrdsp9bnystssa2etb51tjfl: write /var/lib/buildkit/runc-overlayfs/metadata_v2.db: input/output error
.After shutting down memory-intensive tasks in the background, running
docker compose up --build
again produces the following error:unable to get image '<local_image_being_built>': Error response from daemon: failed to get config descriptor: rpc error: code = Unknown desc = blob sha256:dca1980b348c21e5a7c06e90516249201760aff5e718d03ca940f6a00c33d1da expected at /var/lib/desktop-containerd/daemon/io.containerd.content.v1.content/blobs/sha256/dca1980b348c21e5a7c06e90516249201760aff5e718d03ca940f6a00c33d1da: open /var/lib/desktop-containerd/daemon/io.containerd.content.v1.content/blobs/sha256/dca1980b348c21e5a7c06e90516249201760aff5e718d03ca940f6a00c33d1da: input/output error
Running
docker image ls
produces something similar:Error response from daemon: rpc error: code = Unknown desc = blob sha256:5781759b3d27734d4d548fcbaf60b1180dbf4290e708f01f292faa6ae764c5e6 expected at /var/lib/desktop-containerd/daemon/io.containerd.content.v1.content/blobs/sha256/5781759b3d27734d4d548fcbaf60b1180dbf4290e708f01f292faa6ae764c5e6: open /var/lib/desktop-containerd/daemon/io.containerd.content.v1.content/blobs/sha256/5781759b3d27734d4d548fcbaf60b1180dbf4290e708f01f292faa6ae764c5e6: input/output error
Further running
docker system prune -a
results in:Error response from daemon: 26 errors occurred: * rpc error: code = Unknown desc = blob sha256:bf8503f739ee445559e7cc9c324fd7dd9d9c10f10b10f04fb5f2de5741d4a2c1 expected at /var/lib/desktop-containerd/daemon/io.containerd.content.v1.content/blobs/sha256/bf8503f739ee445559e7cc9c324fd7dd9d9c10f10b10f04fb5f2de5741d4a2c1: open /var/lib/desktop-containerd/daemon/io.containerd.content.v1.content/blobs/sha256/bf8503f739ee445559e7cc9c324fd7dd9d9c10f10b10f04fb5f2de5741d4a2c1: input/output error ...
Steps To Reproduce
docker compose up --build
rpc error: code = Unknown desc = blob ...
with a set of file paths that don't exist on my machine.Compose Version
Docker Environment
Anything else?
The text was updated successfully, but these errors were encountered: