Docker/Compose/docker compose up / down

CommandUpdated 3 weeks ago

docker compose up / down

Starts (or tears down) every service defined in docker-compose.yml together, with the network between them already wired up.

#docker #compose

Command

Bring the stack up

SHELL

1docker compose up # foreground, logs from every service interleaved

2docker compose up -d # detached

3docker compose up --build # rebuild images first

Tear down

Stop and remove

SHELL

1docker compose down # stop and remove containers/network

2docker compose down -v # also remove named volumes — deletes data

One service at a time

Scoped commands

SHELL

1docker compose logs -f <service>

2docker compose exec <service> sh

3docker compose restart <service>

More compose commands

Day-to-day

SHELL

1docker compose ps # services of this project

2docker compose build # (re)build images

3docker compose pull # pull newer images

4docker compose up -d --force-recreate # recreate even if unchanged

5docker compose up -d --scale worker=3 # run 3 copies of a service

6docker compose stop / start # pause without removing

7docker compose run --rm api npm test # one-off command in a new container

8docker compose config # print the merged, resolved config

9docker compose -f compose.yml -f compose.prod.yml up -d # layered files

10docker compose -p myproj up -d # custom project name

Up vs down vs stop

Command	Containers	Network	Volumes	Images
`stop`	stopped, kept	kept	kept	kept
`down`	removed	removed	kept	kept
`down -v`	removed	removed	deleted	kept
`down --rmi all`	removed	removed	kept	deleted

up -d after a config change recreates only the services whose config or image changed.

Gotchas

Services reach each other by service name (db:5432), not localhost
depends_on only orders startup; it does not wait for the app to be ready unless you add a healthcheck and condition: service_healthy
Variables in .env next to the compose file are substituted automatically
Code changes need up --build (or a bind mount); plain up reuses the old image

Docker/Compose/docker compose up / down

CommandUpdated 3 weeks ago

docker compose up / down

Starts (or tears down) every service defined in docker-compose.yml together, with the network between them already wired up.

#docker #compose

Command

Bring the stack up

SHELL

1docker compose up # foreground, logs from every service interleaved

2docker compose up -d # detached

3docker compose up --build # rebuild images first

Tear down

Stop and remove

SHELL

1docker compose down # stop and remove containers/network

2docker compose down -v # also remove named volumes — deletes data

One service at a time

Scoped commands

SHELL

1docker compose logs -f <service>

2docker compose exec <service> sh

3docker compose restart <service>

More compose commands

Day-to-day

SHELL

1docker compose ps # services of this project

2docker compose build # (re)build images

3docker compose pull # pull newer images

4docker compose up -d --force-recreate # recreate even if unchanged

5docker compose up -d --scale worker=3 # run 3 copies of a service

6docker compose stop / start # pause without removing

7docker compose run --rm api npm test # one-off command in a new container

8docker compose config # print the merged, resolved config

9docker compose -f compose.yml -f compose.prod.yml up -d # layered files

10docker compose -p myproj up -d # custom project name

Up vs down vs stop

Command	Containers	Network	Volumes	Images
`stop`	stopped, kept	kept	kept	kept
`down`	removed	removed	kept	kept
`down -v`	removed	removed	deleted	kept
`down --rmi all`	removed	removed	kept	deleted

up -d after a config change recreates only the services whose config or image changed.

Gotchas

Services reach each other by service name (db:5432), not localhost
depends_on only orders startup; it does not wait for the app to be ready unless you add a healthcheck and condition: service_healthy
Variables in .env next to the compose file are substituted automatically
Code changes need up --build (or a bind mount); plain up reuses the old image