blob: 241da1f71f68d5ecc49a20fe2485bf67e0a06c6b (
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
|
% podman(1) podman-stop - Stop one or more containers
% Brent Baude
# podman-stop "1" "September 2017" "podman"
## NAME
podman stop - Stop one or more containers
## SYNOPSIS
**podman stop [OPTIONS] CONTAINER [...]**
## DESCRIPTION
Stops one or more containers. You may use container IDs or names as input. The **--timeout** switch
allows you to specify the number of seconds to wait before forcibly stopping the container after the stop command
is issued to the container. The default is 10 seconds. By default, containers are stopped with SIGTERM
and then SIGKILL after the timeout. The SIGTERM default can be overridden by the image used to create the
container and also via command line when creating the container.
## OPTIONS
**--timeout, --time, t**
Timeout to wait before forcibly stopping the container
**--all, -a**
Stop all running containers. This does not include paused containers.
**--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.
## EXAMPLE
podman stop mywebserver
podman stop 860a4b23
podman stop mywebserver 860a4b23
podman stop --timeout 2 860a4b23
podman stop -a
podman stop --latest
## SEE ALSO
podman(1), podman-rm(1)
## HISTORY
September 2018, Originally compiled by Brent Baude <bbaude@redhat.com>
|
