Docker Core
Container Platform — 28 error codes
Reference list of 28 Docker core with meanings, common causes, and related context.
About Docker Core
This collection documents 28 Docker core error codes with independent explanations. Each entry includes the error meaning, common causes, typical scenarios, and related context. FixerCode is an independent reference and is not affiliated with Docker or any vendor mentioned on this site.
Each error code page provides a structured reference: the official meaning, a plain-language explanation, common causes, typical scenarios, and links to related codes within the same core family. Frequently asked questions address common points of confusion.
Showing 28 of 28 error codes
A write under Docker's storage ran out of filesystem space and failed.
The Docker CLI reached no daemon, so every command stops before doing any work.
The daemon answered, but the current Unix user lacks rights on the socket.
A newer client asked for an API version the connected daemon refuses to serve.
The registry refused the pull because the repository is private or unknown.
The registry answered with a 401 asking the client to authenticate first.
The server recognized the caller but refused the specific repository action.
The Hub pull allowance for this address or account ran out inside its window.
The TLS certificate presented by the registry chains to no trusted authority.
The daemon could not bind the published host port because another holder keeps it.
The kernel refused the bind because a live socket already occupies the address.
The network driver could not program the published port mapping for the endpoint.
An exec or attach targeted a container whose main process is not active.
The OCI runtime refused to create the container process from its bundle.
The kernel declined the binary because it was built for another architecture.
BuildKit aborted the build because a step exited with a failing code.
Compose gave up because a dependency container failed its startup condition.
The registry has no manifest for the exact repository and tag requested.
The image reference string violates the naming rules before any lookup.
A container claims the requested human name, and names must stay unique.
A removal request hit a volume that running or stopped containers still mount.
A command referenced a network name or ID the daemon has no record of.
The requested subnet range collides with an address pool already in use.
A command addressed a container name or ID the daemon cannot resolve.
Removal was refused because the container's process is still alive.
The runtime could not launch the exec command inside the running container.
The builder could not locate a Dockerfile at the path the build referenced.
The daemon returned a structured error response carrying the failure detail.