Docker Compose Cheat Sheet

Use this for the default local startup flow.

Useful for long-running local environments.

Useful when Dockerfiles or build contexts changed.

Leaves named volumes unless you add `-v`.

Use carefully because stateful data will be deleted.

Useful after `docker compose stop`.

Containers remain available for `start` later.

Useful after config changes external to the image.

Suspends processes without stopping the containers.

Pair with `pause` during testing.

Great when working from source.

Useful when debugging build issues.

Speeds up iteration on a single app container.

Useful before a deployment or refresh.

Handy in mixed build/image projects.

Useful in CI after a successful build.

Useful for audit and cleanup work.

Use service names to narrow the output.

Helpful during startup and debugging.

Keeps output focused during triage.

Use `bash` when the image includes it.

Common in Debian/Ubuntu based app images.

Useful for migrations, tests, or generators.

Helpful when debugging process models and daemons.

Use `-a` to include stopped containers.

Useful for debugging restarts and recreate loops.

Use this to verify what Compose will actually run.

Useful in scripts and CI checks.

Helps audit stateful resources.

Helpful when organizing optional services.

Useful when you run many stacks locally.

Useful after experimenting with one-off runs.

Useful when graceful stop is hanging.

Useful in automation and test pipelines.