No such container Docker Origin: Platform & cloud Last updated 13 Oct 2026

Error response from daemon: No such container

The container name or ID you used doesn’t exist on this Docker host — it was removed, has another name, or you’re talking to a different daemon/context.

Exact message you may see No such containerError: No such containerError response from daemon: No such container
Explore the map of this error Full error map →
Seen on: Docker

Meaning

Containers created with --rm disappear when they stop, Compose names containers project-service-1, and docker context can point the CLI at another machine.

Common causes

  • Container already removed (--rm, prune)
  • Wrong name (Compose adds project prefix and -1 suffix)
  • Different docker context / remote daemon
  • Truncated or mistyped ID

⚡ Quick fix

  1. List all containers: docker ps -a
  2. Use docker compose exec <service> instead of container names
  3. Check docker context ls

Detailed fix by platform

Docker

  1. bash
    docker ps -a --format '{{.ID}}  {{.Names}}  {{.Status}}'
docker compose exec web sh

How to diagnose

  1. Exists — docker ps -a | grep name
  2. Context — docker context show

🔧 Still not fixed?

Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:

Where this error sits

Origin: Platform & cloud. Errors that are often confused with or caused by this one (click to open):

ACR unauthorized — Azure Container Registry: unauthorized: authentication required, visit https://aka.ms/acr/authorization (AKS ErrImagePull 401) (Azure)ACR unauthorizedConflict container name — Conflict. The container name "/x" is already in use by container … (Docker)Conflict container na…Container failed to start — Cloud Run: The user-provided container failed to start and listen on the port defined provided by the PORT=8080 environment variable (Google Cloud / Firebase)Container failed to s…docker-compose: command not found — docker-compose: command not found / 'compose' is not a docker command (Docker)docker-compose: comma…exec no such file or directory — exec /docker-entrypoint.sh: no such file or directory (CRLF line endings / missing interpreter) (Docker)exec no such file or …Exited (0) — Docker container exits immediately (Exited (0) / Exited (1) right after start) (Docker)Exited (0)is not running — Error response from daemon: Container X is not running (Docker)is not runningthe input device is not a TTY — the input device is not a TTY (Docker)the input device is n…No such c…

Explore the map of this error Full error map →

🧠 Still stuck? Analyze your error

Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.

💬 What worked for others

No tips yet — did something else fix this for you?

Share what worked for you

Tips are checked by an editor before they appear. Links are removed.