Files
podman/docs/podman-rm.1.md
baude 6ab6e2c307 hide --latest on the remote-client
in the case of the remote-client, it was decided to hide the latest
flag to avoid confusion for end-users on what the "last" container,
volume, or pod are.

Signed-off-by: baude <bbaude@redhat.com>
2019-02-22 14:13:08 -06:00

65 lines
1.6 KiB
Markdown

% podman-rm(1)
## NAME
podman\-rm - Remove one or more containers
## SYNOPSIS
**podman rm** [*options*] *container*
## DESCRIPTION
**podman rm** will remove one or more containers from the host. The container name or ID can be used. This does not remove images. Running containers will not be removed without the `-f` option
## OPTIONS
**--all, a**
Remove all containers. Can be used in conjunction with -f as well.
**--force, f**
Force the removal of running and paused containers. Forcing a containers removal also
removes containers from container storage even if the container is not known to podman.
Containers could have been created by a different container engine.
**--latest, -l**
Instead of providing the container name or ID, use the last created container. If you use methods other than Podman
to run containers such as CRI-O, the last started container could be from either of those methods.
The latest option is not supported on the remote client.
**--volumes, -v**
Remove the volumes associated with the container. (Not yet implemented)
## EXAMPLE
Remove a container by its name *mywebserver*
```
podman rm mywebserver
```
Remove several containers by name and container id.
```
podman rm mywebserver myflaskserver 860a4b23
```
Forcibly remove a container by container ID.
```
podman rm -f 860a4b23
```
Remove all containers regardless of its run state.
```
podman rm -f -a
```
Forcibly remove the latest container created.
```
podman rm -f --latest
```
## SEE ALSO
podman(1), podman-rmi(1)
## HISTORY
August 2017, Originally compiled by Ryan Cole <rycole@redhat.com>