1 files changed, 68 insertions, 0 deletions
diff --git a/docs/source/markdown/podman-kill.1.md.in b/docs/source/markdown/podman-kill.1.md.in
new file mode 100644
index 000000000..2788cc694
--- /dev/null
+++ b/docs/source/markdown/podman-kill.1.md.in
@@ -0,0 +1,68 @@
+% 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)
+
+#### **--signal**, **-s**
+
+Signal to send to the container. For more information on Linux signals, refer to *man signal(7)*.
+
+
+## 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>