blob: 7f22113ea0bf1fe9d3113d870e45362a629b6d35 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
|
% 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.
**--sync**
Force a sync of container state with the OCI runtime before attempting to remove.
In some cases, a container's state in the runtime can become out of sync with Podman's state,
which can cause Podman to refuse to remove containers because it believes they are still running.
A sync will resolve this issue.
**--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>
|
