blob: 46d7f5c6b809e42cc7a97defdcfbaa6857ebe1ea (
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-kill(1)
## NAME
podman\-kill - Kill the main process in one or more containers
## SYNOPSIS
**podman kill** [*options*] [*container* ...]
**podman container kill** [*options*] [*container* ...]
## DESCRIPTION
The main process inside each container specified will be sent SIGKILL, or any signal specified with option --signal.
## OPTIONS
#### **--all**, **-a**
Signal all running and paused containers.
@@option cidfile.read
#### **--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. (This option is not available with the remote Podman client, including Mac and Windows (excluding WSL2) machines)
@@option signal
## EXAMPLE
Kill container with a given name
```
podman kill mywebserver
```
Kill container with a given ID
```
podman kill 860a4b23
```
Terminate container by sending `TERM` signal
```
podman kill --signal TERM 860a4b23
```
Kill the latest container created by Podman
```
podman kill --latest
```
Terminate all containers by sending `KILL` signal
```
podman kill --signal KILL -a
```
Kill container using ID specified in a given files
```
podman kill --cidfile /home/user/cidfile-1
podman kill --cidfile /home/user/cidfile-1 --cidfile ./cidfile-2
```
## SEE ALSO
**[podman(1)](podman.1.md)**, **[podman-stop(1)](podman-stop.1.md)**
## HISTORY
September 2017, Originally compiled by Brent Baude <bbaude@redhat.com>
|
