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
1.0 KiB
% podman(1) podman-wait - Waits on a container % Brent Baude
podman-wait "1" "September 2017" "podman"
NAME
podman-wait - Waits on one or more containers to stop and prints exit code
SYNOPSIS
podman wait [--help|-h]
DESCRIPTION
Waits on one or more containers to stop. The container can be referred to by its name or ID. In the case of multiple containers, podman will wait on each consecutively. After the container stops, the container's return code is printed.
**podman [GLOBAL OPTIONS] wait **
GLOBAL OPTIONS
--help, -h Print usage statement
--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.
EXAMPLES
podman wait mywebserver
podman wait --latest
podman wait 860a4b23
podman wait mywebserver myftpserver
SEE ALSO
podman(1), crio(8)
HISTORY
September 2017, Originally compiled by Brent Baudebbaude@redhat.com