1podman-start(1)() podman-start(1)()
2
6 podman-start - Start one or more containers
7
10 podman start [options] container ...
11 podman container start [options] container ...
14
17 Start one or more containers. You may use container IDs or names as
18 input. The attach and interactive options cannot be used to override
19 the --tty and --interactive options from when the container was cre‐
20 ated. If you attempt to start a running container with the --attach op‐
21 tion, podman will simply attach to the container.
22
25 --attach, -a
26 Attach container's STDOUT and STDERR. The default is false. This op‐
27 tion cannot be used when starting multiple containers.
28 --detach-keys=sequence
31 Specify the key sequence for detaching a container. Format is a single
32 character [a-Z] or one or more ctrl-<value> characters where <value> is
33 one of: a-z, @, ^, [, , or _. Specifying "" will disable this feature.
34 The default is ctrl-p,ctrl-q.
35 --interactive, -i
38 Attach container's STDIN. The default is false.
39 --latest, -l
42 Instead of providing the container name or ID, use the last created
43 container. If you use methods other than Podman to run containers such
44 as CRI-O, the last started container could be from either of those
45 methods. (This option is not available with the remote Podman client)
46 --sig-proxy=true|false
49 Proxy received signals to the process (non-TTY mode only). SIGCHLD,
50 SIGSTOP, and SIGKILL are not proxied. The default is true when attach‐
51 ing, false otherwise.
52 --all
55 Start all the containers created by Podman, default is only running
56 containers.
57 --filter, -f
60 Filter what containers are going to be started from the given argu‐
61 ments. Multiple filters can be given with multiple uses of the --fil‐
62 ter flag. Filters with the same key work inclusive with the only ex‐
63 ception being label which is exclusive. Filters with different keys al‐
64 ways work exclusive.
65 Valid filters are listed below:
68 ┌─────────┬───────────────────────────────┐
71 │Filter │ Description │
72 ├─────────┼───────────────────────────────┤
73 │id │ [ID] Container's ID (accepts │
74 │ │ regex) │
75 ├─────────┼───────────────────────────────┤
76 │name │ [Name] Container's name (ac‐ │
77 │ │ cepts regex) │
78 ├─────────┼───────────────────────────────┤
79 │label │ [Key] or [Key=Value] Label │
80 │ │ assigned to a container │
81 ├─────────┼───────────────────────────────┤
82 │exited │ [Int] Container's exit code │
83 ├─────────┼───────────────────────────────┤
84 │status │ [Status] Container's status: │
85 │ │ 'created', 'exited', │
86 │ │ 'paused', 'running', 'un‐ │
87 │ │ known' │
88 ├─────────┼───────────────────────────────┤
89 │ancestor │ [ImageName] Image or descen‐ │
90 │ │ dant used to create container │
91 ├─────────┼───────────────────────────────┤
92 │before │ [ID] or [Name] Containers │
93 │ │ created before this container │
94 ├─────────┼───────────────────────────────┤
95 │since │ [ID] or [Name] Containers │
96 │ │ created since this container │
97 ├─────────┼───────────────────────────────┤
98 │volume │ [VolumeName] or [Mountpoint‐ │
99 │ │ Destination] Volume mounted │
100 │ │ in container │
101 ├─────────┼───────────────────────────────┤
102 │health │ [Status] healthy or unhealthy │
103 ├─────────┼───────────────────────────────┤
104 │pod │ [Pod] name or full or partial │
105 │ │ ID of pod │
106 ├─────────┼───────────────────────────────┤
107 │network │ [Network] name or full ID of │
108 │ │ network │
109 └─────────┴───────────────────────────────┘
110
112 podman start mywebserver
113 podman start 860a4b231279 5421ab43b45
116 podman start --interactive --attach 860a4b231279
119 podman start -i -l
122
125 podman(1), podman-create(1)
126
129 November 2018, Originally compiled by Brent Baude bbaude@redhat.com
130 ⟨mailto:bbaude@redhat.com⟩
131 podman-start(1)()