.nh .TH podman-start 1 .SH NAME .PP podman-start - Start one or more containers .SH SYNOPSIS .PP \fBpodman start\fP [\fIoptions\fP] \fIcontainer\fP ... .PP \fBpodman container start\fP [\fIoptions\fP] \fIcontainer\fP ... .SH DESCRIPTION .PP Start one or more containers. You may use container IDs or names as input. The \fIattach\fP and \fIinteractive\fP options cannot be used to override the \fI--tty\fP and \fI--interactive\fP options from when the container was created. If you attempt to start a running container with the \fI--attach\fP option, podman will simply attach to the container. .SH OPTIONS .SS \fB--all\fP .PP Start all the containers created by Podman, default is only running containers. .SS \fB--attach\fP, \fB-a\fP .PP Attach container's STDOUT and STDERR. The default is false. This option cannot be used when starting multiple containers. .SS \fB--detach-keys\fP=\fIsequence\fP .PP Specify the key sequence for detaching a container. Format is a single character \fB\fC[a-Z]\fR or one or more \fB\fCctrl-\fR characters where \fB\fC\fR is one of: \fB\fCa-z\fR, \fB\fC@\fR, \fB\fC^\fR, \fB\fC[\fR, \fB\fC,\fR or \fB\fC_\fR\&. Specifying "" will disable this feature. The default is \fIctrl-p,ctrl-q\fP\&. .PP This option can also be set in \fBcontainers.conf\fP(5) file. .SS \fB--filter\fP, \fB-f\fP .PP Filter what containers are going to be started from the given arguments. Multiple filters can be given with multiple uses of the --filter flag. Filters with the same key work inclusive with the only exception being \fB\fClabel\fR which is exclusive. Filters with different keys always work exclusive. .PP Valid filters are listed below: .TS allbox; l l l l . \fB\fC\fBFilter\fP\fR \fB\fC\fBDescription\fP\fR id T{ [ID] Container's ID (accepts regex) T} name T{ [Name] Container's name (accepts regex) T} label T{ [Key] or [Key=Value] Label assigned to a container T} exited [Int] Container's exit code status T{ [Status] Container's status: 'created', 'exited', 'paused', 'running', 'unknown' T} ancestor T{ [ImageName] Image or descendant used to create container T} before T{ [ID] or [Name] Containers created before this container T} since T{ [ID] or [Name] Containers created since this container T} volume T{ [VolumeName] or [MountpointDestination] Volume mounted in container T} health [Status] healthy or unhealthy pod T{ [Pod] name or full or partial ID of pod T} network T{ [Network] name or full ID of network T} .TE .SS \fB--interactive\fP, \fB-i\fP .PP When set to \fBtrue\fP, keep stdin open even if not attached. The default is \fBfalse\fP\&. .SS \fB--latest\fP, \fB-l\fP .PP 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. (This option is not available with the remote Podman client, including Mac and Windows (excluding WSL2) machines) .SS \fB--sig-proxy\fP .PP Proxy received signals to the container process (non-TTY mode only). SIGCHLD, SIGSTOP, and SIGKILL are not proxied. .PP The default is \fBtrue\fP when attaching, \fBfalse\fP otherwise. .SH EXAMPLE .PP podman start mywebserver .PP podman start 860a4b231279 5421ab43b45 .PP podman start --interactive --attach 860a4b231279 .PP podman start -i -l .SH SEE ALSO .PP \fBpodman(1)\fP .SH HISTORY .PP November 2018, Originally compiled by Brent Baude bbaude@redhat.com \[la]mailto:bbaude@redhat.com\[ra]