What Docker Could Not Find on This Daemon
Docker could not find the referenced container, image, network, or volume ID, usually because it was deleted, mistyped, or belongs to another context.
Check the current context and object ID
Confirm the active Docker context and host before touching the image name with docker context ls and docker context show, check whether the daemon is reachable from this shell with docker version or docker info and make sure the server section appears, and if you are on Linux, inspect socket ownership and group access directly with ls -la /var/run/docker.sock and groups.
Use the correct object ID or context
List objects on the current daemon and confirm the ID exists, check active context with docker context show, and retry using a name instead of a short ID if possible.
Why This Daemon Cannot Resolve the ID
The object was deleted or never existed on this daemon.
You are talking to a different Docker context/daemon than you think.
Verify the Object Resolves on This Daemon
Re-run the command with the correct ID or name, and confirm the object shows up in the relevant docker <resource> ls output.
Typical Output
Error response from daemon: id not foundAvoid Version and Source Drift
To prevent this, avoid relying on ephemeral IDs across scripts, prefer names and labels, and keep contexts explicit in CI scripts.
How Docker resolves IDs on the current daemon
The Docker CLI is only a client. Most commands talk to the Docker daemon over a local socket or a remote API, and that control plane has to be healthy before Docker can do anything with images, containers, or volumes. When that path is broken, Docker fails immediately because it never gets far enough to inspect the image or run the container command you asked for.