be311fba7b
This makes it so when calling `docker run --rm`, or `docker rm -v`, only volumes specified without a name, e.g. `docker run -v /foo` instead of `docker run -v awesome:/foo` are removed. Note that all volumes are named, some are named by the user, some get a generated name. This is specifically about how the volume was specified on `run`, assuming that if the user specified it with a name they expect it to persist after the container is cleaned up. Signed-off-by: Brian Goff <cpuguy83@gmail.com>
61 lines
1.7 KiB
Markdown
61 lines
1.7 KiB
Markdown
<!--[metadata]>
|
|
+++
|
|
title = "rm"
|
|
description = "The rm command description and usage"
|
|
keywords = ["remove, Docker, container"]
|
|
[menu.main]
|
|
parent = "smn_cli"
|
|
+++
|
|
<![end-metadata]-->
|
|
|
|
# rm
|
|
|
|
Usage: docker rm [OPTIONS] CONTAINER [CONTAINER...]
|
|
|
|
Remove one or more containers
|
|
|
|
-f, --force Force the removal of a running container (uses SIGKILL)
|
|
--help Print usage
|
|
-l, --link Remove the specified link
|
|
-v, --volumes Remove the volumes associated with the container
|
|
|
|
## Examples
|
|
|
|
$ docker rm /redis
|
|
/redis
|
|
|
|
This will remove the container referenced under the link
|
|
`/redis`.
|
|
|
|
$ docker rm --link /webapp/redis
|
|
/webapp/redis
|
|
|
|
This will remove the underlying link between `/webapp` and the `/redis`
|
|
containers removing all network communication.
|
|
|
|
$ docker rm --force redis
|
|
redis
|
|
|
|
The main process inside the container referenced under the link `/redis` will receive
|
|
`SIGKILL`, then the container will be removed.
|
|
|
|
$ docker rm $(docker ps -a -q)
|
|
|
|
This command will delete all stopped containers. The command
|
|
`docker ps -a -q` will return all existing container IDs and pass them to
|
|
the `rm` command which will delete them. Any running containers will not be
|
|
deleted.
|
|
|
|
$ docker rm -v redis
|
|
redis
|
|
|
|
This command will remove the container and any volumes associated with it.
|
|
Note that if a volume was specified with a name, it will not be removed.
|
|
|
|
$ docker create -v awesome:/foo -v /bar --name hello redis
|
|
hello
|
|
$ docker rm -v hello
|
|
|
|
In this example, the volume for `/foo` will remain intact, but the volume for
|
|
`/bar` will be removed. The same behavior holds for volumes inherited with
|
|
`--volumes-from`.
|