mirror of
https://github.com/containers/podman.git
synced 2025-07-30 20:02:37 +08:00
c9c2f644da
In each options/foo.md, keep a list of where the option is used. This will be valuable to anyone making future edits, and to those reviewing those edits. This may be a controversial commit, because those crossref lists are autogenerated as a side effect of the script that reads them. It definitely violates POLA. And one day, some kind person will reconcile (e.g.) --label, using it in more man pages, and maybe forget to git-commit the rewritten file, and CI will fail. I think this is a tough tradeoff, but worth doing. Without this, it's much too easy for someone to change an option file in a way that renders it inapplicable/misleading for some podman commands. Signed-off-by: Ed Santiago <santiago@redhat.com>
15 lines
625 B
Markdown
15 lines
625 B
Markdown
####> This option file is used in:
|
|
####> podman create, run
|
|
####> If you edit this file, make sure your changes
|
|
####> are applicable to all of those.
|
|
#### **--attach**, **-a**=*stdin* | *stdout* | *stderr*
|
|
|
|
Attach to STDIN, STDOUT or STDERR.
|
|
|
|
In foreground mode (the default when **-d**
|
|
is not specified), **podman run** can start the process in the container
|
|
and attach the console to the process's standard input, output, and
|
|
error. It can even pretend to be a TTY (this is what most command-line
|
|
executables expect) and pass along signals. The **-a** option can be set for
|
|
each of **stdin**, **stdout**, and **stderr**.
|