f30bde6adb
these markdown files are not consumed directly in the docs, but only their content is included through the YAML does, so there's no need to have these comments in them Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2.1 KiB
title, description, keywords
| title | description | keywords |
|---|---|---|
| rm | The rm command description and usage | remove, Docker, container |
rm
Usage: docker rm [OPTIONS] CONTAINER [CONTAINER...]
Remove one or more containers
Options:
-f, --force Force the removal of a running container (uses SIGKILL)
--help Print usage
-l, --link Remove the specified link
-v, --volumes Remove anonymous volumes associated with the container
Examples
Remove a container
This will remove the container referenced under the link
/redis.
$ docker rm /redis
/redis
Remove a link specified with --link on the default bridge network
This will remove the underlying link between /webapp and the /redis
containers on the default bridge network, removing all network communication
between the two containers. This does not apply when --link is used with
user-specified networks.
$ docker rm --link /webapp/redis
/webapp/redis
Force-remove a running container
This command will force-remove a running container.
$ 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.
Remove all stopped containers
$ 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.
Remove a container and its volumes
$ 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.
Remove a container and selectively remove volumes
$ 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.