Fix it fast
Most likely: The image is not present in the local image store for the Docker daemon/context running the command.
1. Confirm this is your error
Error: No such image: <image-id>2. Check the cause
docker context show
docker image ls --digests
docker image inspect <image-or-tag>
docker ps -a3. Apply the safe fix
# Pull or build the exact image tag before using it locally.
docker pull <image:tag>
# Or build it with the exact tag the later command expects.
docker build -t <image:tag> .
docker run --rm <image:tag>4. Verify it works
docker image inspect <image:tag>
docker run --rm <image:tag>Don't use unsafe shortcuts
- Do not use image IDs copied from another machine, CI job, or Docker context.
- Do not assume a previous build step ran on the same Docker daemon unless the job logs prove it.
- Do not confuse this with a remote missing tag, this error is about the local image store.
What Docker Could Not Find on This Daemon
Docker cannot find that image locally, so the image ID or tag is wrong, was removed, or was never pulled onto this machine.
Check the image on the current daemon
Check the active daemon and context with docker context show.
List local images on that daemon with docker image ls --digests --no-trunc.
If CI built the image earlier, confirm the build or pull step ran on the same runner and context.
Build, pull, or reference the right local image
List local images on the current daemon and confirm the expected tag or ID exists.
If the image should be present locally, pull or build it again with the exact tag the later command expects.
If the script is using a short ID copied from elsewhere, switch to a stable tag or use the right Docker context.
Why This Daemon Cannot Find the Image
The local image ID or tag is wrong.
The image was removed or never existed on this daemon.
The script is using an image ID or tag from another machine, runner, or Docker context.
Verify the Image Exists on This Daemon
Run docker image inspect <image-or-tag> on the current daemon and confirm it returns metadata, and retry the original Docker command and confirm it now resolves the image locally.
Avoid Version and Source Drift
To prevent this, prefer stable tags or digests over short ephemeral IDs in scripts, and make pull or build steps explicit before commands that expect the image to exist locally.
How Docker resolves local image references
Commands like docker run, docker tag, and docker rmi first resolve the image reference against the local image store on the current daemon.
If no local image ID or tag matches, Docker fails before any registry lookup happens.