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-rm - Remove one or more containers % Ryan Cole
podman-rm "1" "August 2017" "podman"
NAME
podman-rm - Remove one or more containers
SYNOPSIS
podman rm [options [...]] container
DESCRIPTION
podman rm will remove one or more containers from the host. The container name or ID can be used. This does not remove images. Running containers will not be removed without the -f option
OPTIONS
--force, f
Force the removal of a running container
--all, a
Remove all containers. Can be used in conjunction with -f as well.
--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 rm mywebserver
podman rm mywebserver myflaskserver 860a4b23
podman rm -f 860a4b23
podman rm -f -a
podman rm -f --latest
SEE ALSO
podman(1), podman-rmi(1)
HISTORY
August 2017, Originally compiled by Ryan Cole rycole@redhat.com