docker-compose-start

start existing Compose service containers without recreating them

TLDR

Start all services that already have containers

$ docker compose start

Start named services only

$ docker compose start [web] [db]

Wait until services are running or healthy

$ docker compose start --wait

Wait, with a timeout in seconds

$ docker compose start --wait --wait-timeout [60]

Dry-run the start (global Compose flag)

$ docker compose --dry-run start

SYNOPSIS

docker compose start [options] [SERVICE...]

docker compose start starts existing containers for one or more services in a Compose project. It does not create missing containers; use docker compose up (or create then start) if the service has never been created.Stopped containers keep their filesystem, networks, and volumes. This is the counterpart to docker compose stop, which pauses without removing. docker compose down removes containers; start cannot bring those back.

PARAMETERS

--wait

Wait until services are running or healthy. Implies detached mode.

--wait-timeout seconds

Maximum seconds to wait when --wait is set.

INSTALL

sudo apt install docker-compose

sudo dnf install docker-compose

sudo pacman -S docker-compose

sudo apk add docker-cli-compose

sudo zypper install docker-compose

brew install docker-compose

nix profile install nixpkgs#docker-compose

CAVEATS

Services without an existing container are skipped or error depending on Compose version; they are not created. Health wait needs a healthcheck in the Compose file. Project selection still uses -f, -p, and the working directory as with other Compose commands.

HISTORY

The standalone `docker-compose start` verb moved to the Compose V2 plugin invoked as docker compose start.

RESOURCES

Documentation · Homepage