Files
podman/docs/podman-rm.1.md
Matthew Heon e5335fd74c Remove --sync flag from podman rm
Per discussion with Dan, it would be better to automatically
handle potential runtime errors by automatically syncing if they
occur. Retaining the flag for `ps` makes sense, as we won't even
be calling the OCI runtime and as such won't see errors if the
state desyncs, but rm can be handled automatically.

The automatic desync handling code will take some additional work
so we'll land this as-is (sync on ps is enough to solve most
desync issues).

Signed-off-by: Matthew Heon <mheon@redhat.com>
2018-12-06 09:10:45 -05:00

61 lines
1.3 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
**--force, f**
Force the removal of a running and paused containers
**--all, a**
Remove all containers. Can be used in conjunction with -f as well.
**--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.
**--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>