Start a Docker Compose stack

Low risk
What do risk levels mean?
Read-only
Inspects state without changing anything.
Low risk
Reversible with a routine follow-up command.
Medium risk
Changes state; undo path documented.
Destructive
Deletes or overwrites; confirmation required.

Starts all services defined in the compose file of the current directory in the background, creating containers, networks, and volumes as needed.

dockercomposeupservices

Commands

List the services the compose file defines before starting them

docker compose config --services

Create and start all services in the background

docker compose up --detach

Show the status of every service in the stack

docker compose ps

Verification

docker compose ps

Each service shows a running (Up) state; services with healthchecks show healthy once they pass.

Undo

Stop and remove the stack's containers and networks; named volumes are kept

docker compose down

Pitfalls

  • Run from the directory containing compose.yaml / docker-compose.yml, or pass --file explicitly.
  • up reuses existing containers when configuration is unchanged; add --build to rebuild images from local Dockerfiles first.
  • Port conflicts with already-running containers make individual services fail to start; check docker compose logs for the failing service.

Related