From 754bbf7a25a8dda49b5d08ef0d0443bbf5af0e36 Mon Sep 17 00:00:00 2001 From: Craig Jennings Date: Sun, 7 Apr 2024 13:41:34 -0500 Subject: new repository --- ...ine%2Freference%2Fcommandline%2Frm%2Findex.html | 30 ++++++++++++++++++++++ 1 file changed, 30 insertions(+) create mode 100644 devdocs/docker/engine%2Freference%2Fcommandline%2Frm%2Findex.html (limited to 'devdocs/docker/engine%2Freference%2Fcommandline%2Frm%2Findex.html') diff --git a/devdocs/docker/engine%2Freference%2Fcommandline%2Frm%2Findex.html b/devdocs/docker/engine%2Freference%2Fcommandline%2Frm%2Findex.html new file mode 100644 index 00000000..f75661b0 --- /dev/null +++ b/devdocs/docker/engine%2Freference%2Fcommandline%2Frm%2Findex.html @@ -0,0 +1,30 @@ +

docker rm


Remove one or more containers

Usage

$ docker rm [OPTIONS] CONTAINER [CONTAINER...]
+

For example uses of this command, refer to the examples section below.

Options

Name, shorthand Default Description
+--force , -f + Force the removal of a running container (uses SIGKILL)
+--link , -l + Remove the specified link
+--volumes , -v + Remove anonymous volumes associated with the container

Examples

Remove a container

This removes the container referenced under the link /redis.

$ docker rm /redis
+
+/redis
+

Remove a link specified with --link on the default bridge network

This removes 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 force-removes 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

Use the docker container prune command to remove all stopped containers, or refer to the docker system prune command to remove unused containers in addition to other Docker resources, such as (unused) images and networks.

Alternatively, you can use the docker ps with the -q / --quiet option to generate a list of container IDs to remove, and use that list as argument for the docker rm command.

Combining commands can be more flexible, but is less portable as it depends on features provided by the shell, and the exact syntax may differ depending on what shell is used. To use this approach on Windows, consider using PowerShell or Bash.

The example below uses docker ps -q to print the IDs of all containers that have exited (--filter status=exited), and removes those containers with the docker rm command:

$ docker rm $(docker ps --filter status=exited -q)
+

Or, using the xargs Linux utility;

$ docker ps --filter status=exited -q | xargs docker rm
+

Remove a container and its volumes

$ docker rm -v redis
+redis
+

This command removes 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 remains intact, but the volume for /bar is removed. The same behavior holds for volumes inherited with --volumes-from.

+

+ © 2019 Docker, Inc.
Licensed under the Apache License, Version 2.0.
Docker and the Docker logo are trademarks or registered trademarks of Docker, Inc. in the United States and/or other countries.
Docker, Inc. and other parties may also have trademark rights in other terms used herein.
+ https://docs.docker.com/engine/reference/commandline/rm/ +

+
-- cgit v1.2.3