174afeb974
Clarify behaviour of rm and down
(cherry picked from commit 3d3f331404)
Signed-off-by: Sven Dowideit <SvenDowideit@home.org.au>
29 lines
757 B
Markdown
29 lines
757 B
Markdown
<!--[metadata]>
|
|
+++
|
|
title = "rm"
|
|
description = "Removes stopped service containers."
|
|
keywords = ["fig, composition, compose, docker, orchestration, cli, rm"]
|
|
[menu.main]
|
|
identifier="rm.compose"
|
|
parent = "smn_compose_cli"
|
|
+++
|
|
<![end-metadata]-->
|
|
|
|
# rm
|
|
|
|
```
|
|
Usage: rm [options] [SERVICE...]
|
|
|
|
Options:
|
|
-f, --force Don't ask to confirm removal
|
|
-v Remove any anonymous volumes attached to containers
|
|
-a, --all Also remove one-off containers created by
|
|
docker-compose run
|
|
```
|
|
|
|
Removes stopped service containers.
|
|
|
|
By default, anonymous volumes attached to containers will not be removed. You
|
|
can override this with `-v`. To list all volumes, use `docker volume ls`.
|
|
|
|
Any data which is not in a volume will be lost.
|