99d180efcc
This fixes an issue where if you did man -k podman-run podman-run (1) - (unknown subject) Now you will see man -k podman-run podman-run (1) - Run a command in a new container More importantly man -k containers | grep podman podman (1) - Simple management tool for containers and images podman-kill (1) - Kills one or more containers with a signal podman-pause (1) - Pause one or more containers podman-ps (1) - Prints out information about containers podman-rm (1) - Remove one or more containers podman-start (1) - Start one or more containers podman-stats (1) - Display a live stream of 1 or more containers' resource usage statistics podman-stop (1) - Stop one or more containers podman-unpause (1) - Unpause one or more containers podman-wait (1) - Waits on one or more containers to stop and prints exit code Signed-off-by: Daniel J Walsh <dwalsh@redhat.com> Closes: #676 Approved by: mheon
979 B
% podman(1) podman-kill- Kill one or more containers with a signal % Brent Baude
podman-kill"1" "September 2017" "podman"
NAME
podman-kill - Kills one or more containers with a signal
SYNOPSIS
podman kill [OPTIONS] CONTAINER [...]
DESCRIPTION
The main process inside each container specified will be sent SIGKILL, or any signal specified with option --signal.
OPTIONS
--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.
--signal, s
Signal to send to the container. For more information on Linux signals, refer to man signal(7).
EXAMPLE
podman kill mywebserver
podman kill 860a4b23
podman kill --signal TERM 860a4b23
podman kill --latest
SEE ALSO
podman(1), podman-stop(1)
HISTORY
September 2017, Originally compiled by Brent Baude bbaude@redhat.com