blob: dd89694ece26e5ee849d9d992ffe5441eebacde4 (
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
|
% podman-pod-rm(1)
## NAME
podman\-pod\-rm - Remove one or more stopped pods and containers
## SYNOPSIS
**podman pod rm** [*options*] *pod*
## DESCRIPTION
**podman pod rm** will remove one or more stopped pods and their containers from the host. The pod name or ID can be used. The \-f option stops all containers and then removes them before removing the pod.
## OPTIONS
**--all**, **-a**
Remove all pods. Can be used in conjunction with \-f as well.
**--ignore**, **-i**
Ignore errors when specified pods are not in the container store. A user might
have decided to manually remove a pod which would lead to a failure during the
ExecStop directive of a systemd service referencing that pod.
**--latest**, **-l**
Instead of providing the pod name or ID, remove the last created pod.
The latest option is not supported on the remote client.
**--force**, **-f**
Stop running containers and delete all stopped containers before removal of pod.
**--pod-id-file**
Read pod ID from the specified file and remove the pod. Can be specified multiple times.
## EXAMPLE
podman pod rm mywebserverpod
podman pod rm mywebserverpod myflaskserverpod 860a4b23
podman pod rm -f 860a4b23
podman pod rm -f -a
podman pod rm -fa
podman pod rm --pod-id-file /path/to/id/file
## Exit Status
**0** All specified pods removed
**1** One of the specified pods did not exist, and no other failures
**2** One of the specified pods is attached to a container
**125** The command fails for any other reason
## SEE ALSO
podman-pod(1)
## HISTORY
July 2018, Originally compiled by Peter Hunt <pehunt@redhat.com>
|
