# docker start: Start Stopped Containers

> How docker start works: restarting an existing stopped container, attaching, and why start differs from run in CI.

Source: https://latchkey.dev/learn/command-reference/docker-start-command  
Updated: 2026-06-25

Restart a container you already created, keeping its config and data.

docker start launches one or more stopped containers, reusing their existing configuration and writable layer. This page covers attaching and how it differs from docker run.

## What it does

docker start re-runs an existing container that was previously stopped or exited. Unlike docker run it does not create a new container, so any data in the container layer persists.

## Common usage

```Terminal
docker start web
docker start -a web                    # attach to stdout/stderr
docker start -ai web                   # attach + interactive
```

## Common errors in CI

"Error: No such container" means the container was removed (e.g. it ran with --rm, which deletes it on exit) - you cannot start a removed container; use docker run again. Without -a, docker start returns immediately and the container runs detached, which can confuse CI scripts expecting to see output; add -a to stream logs.

## FAQ

### docker start: Start Stopped Containers?

docker start launches one or more stopped containers, reusing their existing configuration and writable layer. This page covers attaching and how it differs from docker run.

### What it does?

docker start re-runs an existing container that was previously stopped or exited. Unlike docker run it does not create a new container, so any data in the container layer persists.

### Common errors in CI?

"Error: No such container" means the container was removed (e.g. it ran with --rm, which deletes it on exit) - you cannot start a removed container; use docker run again. Without -a, docker start returns immediately and the container runs detached, which can confuse CI scripts expecting to see output; add -a to stream logs.

---

Latchkey runs CI/CD that repairs its own failures. Agent entry points: https://latchkey.dev/agent.txt, https://latchkey.dev/openapi.json, https://latchkey.dev/llms.txt