Files
podman/docs/podman-start.1.md
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.6 KiB

% podman(1) podman-start - Stop one or more containers % Brent Baude

podman-start "1" "November 2017" "podman"

NAME

podman-start - Start one or more containers

SYNOPSIS

podman start [OPTIONS] CONTAINER [...]

DESCRIPTION

Start one or more containers. You may use container IDs or names as input. The attach and interactive options cannot be used to override the --tty* and --interactive options from when the container was created. If you attempt to start a running container with the --attach option, podman will simply attach to the container.

OPTIONS

--attach, -a

Attach container's STDOUT and STDERR. The default is false. This option cannot be used when starting multiple containers.

--detach-keys

Override the key sequence for detaching a container. Format is a single character [a-Z] or ctrl- where is one of: a-z, @, ^, [, , or _.

--interactive, -i

Attach container's STDIN. The default is false.

--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.

--sig-proxy=true|false Proxy received signals to the process (non-TTY mode only). SIGCHLD, SIGSTOP, and SIGKILL are not proxied. The default is false.

EXAMPLE

podman start mywebserver

podman start 860a4b23 5421ab4

podman start -i -a 860a4b23

podman start -i -l

SEE ALSO

podman(1), podman-create(1)

HISTORY

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