1podman-stop(1)() podman-stop(1)()
2
3
4
6 podman-stop - Stop one or more running containers
7
8
10 podman stop [options] container ...
11
12
13 podman container stop [options] container ...
14
15
17 Stops one or more containers. You may use container IDs or names as
18 input. The --timeout switch allows you to specify the number of seconds
19 to wait before forcibly stopping the container after the stop command
20 is issued to the container. The default is 10 seconds. By default, con‐
21 tainers are stopped with SIGTERM and then SIGKILL after the timeout.
22 The SIGTERM default can be overridden by the image used to create the
23 container and also via command line when creating the container.
24
25
27 --all, -a
28
29
30 Stop all running containers. This does not include paused containers.
31
32
33 --latest, -l
34
35
36 Instead of providing the container name or ID, use the last created
37 container. If you use methods other than Podman to run containers such
38 as CRI-O, the last started container could be from either of those
39 methods.
40
41
42 The latest option is not supported on the remote client.
43
44
45 --timeout, --time, t=time
46
47
48 Timeout to wait before forcibly stopping the container
49
50
52 podman stop mywebserver
53
54
55 podman stop 860a4b235279
56
57
58 podman stop mywebserver 860a4b235279
59
60
61 podman stop --timeout 2 860a4b235279
62
63
64 podman stop -a
65
66
67 podman stop --latest
68
69
71 podman(1), podman-rm(1)
72
73
75 September 2018, Originally compiled by Brent Baude bbaude@redhat.com
76 ⟨mailto:bbaude@redhat.com⟩
77
78
79
80 podman-stop(1)()