Skip to content

compose_down.md

Latest commit

 

History

History
58 lines (39 loc) · 2.92 KB

compose_down.md

File metadata and controls

58 lines (39 loc) · 2.92 KB

docker compose down

Stops containers and removes containers, networks, volumes, and images created by up.

By default, the only things removed are:

  • Containers for services defined in the Compose file.
  • Networks defined in the networks section of the Compose file.
  • The default network, if one is used.

Networks and volumes defined as external are never removed.

Anonymous volumes are not removed by default. However, as they don’t have a stable name, they are not automatically mounted by a subsequent up. For data that needs to persist between updates, use explicit paths as bind mounts or named volumes.

Use --all to remove every resource for the project, including services from inactive profiles and orphan containers.

Examples

$ docker compose down
$ docker compose down -v --remove-orphans
$ docker compose down --all -v

Options

Name Type Default Description
--all bool Remove all resources for the project, including inactive profile services and orphan containers
--dry-run bool Execute command in dry run mode
--remove-orphans bool Remove containers for services not defined in the Compose file
--rmi string Remove images used by services. "local" remove only images that don't have a custom tag ("local"|"all")
-t, --timeout int 0 Specify a shutdown timeout in seconds
-v, --volumes bool Remove named volumes declared in the "volumes" section of the Compose file and anonymous volumes attached to containers

Description

Stops containers and removes containers, networks, volumes, and images created by up.

By default, the only things removed are:

  • Containers for services defined in the Compose file.
  • Networks defined in the networks section of the Compose file.
  • The default network, if one is used.

Networks and volumes defined as external are never removed.

Anonymous volumes are not removed by default. However, as they don’t have a stable name, they are not automatically mounted by a subsequent up. For data that needs to persist between updates, use explicit paths as bind mounts or named volumes.

Use --all to remove every resource for the project, including services from inactive profiles and orphan containers.