mirror of
https://github.com/containers/podman.git
synced 2025-10-29 00:38:34 +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>
14 lines
686 B
Markdown
14 lines
686 B
Markdown
####> This option file is used in:
|
|
####> podman create, exec, run
|
|
####> If you edit this file, make sure your changes
|
|
####> are applicable to all of those.
|
|
#### **--tty**, **-t**
|
|
|
|
Allocate a pseudo-TTY. The default is **false**.
|
|
|
|
When set to **true**, Podman will allocate a pseudo-tty and attach to the standard
|
|
input of the container. This can be used, for example, to run a throwaway
|
|
interactive shell.
|
|
|
|
**NOTE**: The --tty flag prevents redirection of standard output. It combines STDOUT and STDERR, it can insert control characters, and it can hang pipes. This option should only be used when run interactively in a terminal. When feeding input to Podman, use -i only, not -it.
|