mirror of https://github.com/containers/podman synced 2024-10-21 09:45:32 +00:00

Daniel J Walsh 99d180efcc Modify man pages so they compile correctly in mandb

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

2018-04-26 13:46:14 +00:00

1.4 KiB

Raw Blame History

% 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

HISTORY

September 2018, Originally compiled by Brent Baude bbaude@redhat.com

1.4 KiB Raw Blame History