mirror of
https://github.com/containers/podman.git
synced 2025-11-01 22:32:50 +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>
17 lines
817 B
Markdown
17 lines
817 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.
|
|
#### **--log-driver**=*driver*
|
|
|
|
Logging driver for the container. Currently available options are **k8s-file**, **journald**, **none** and **passthrough**, with **json-file** aliased to **k8s-file** for scripting compatibility. (Default **journald**).
|
|
|
|
The podman info command below will display the default log-driver for the system.
|
|
```
|
|
$ podman info --format '{{ .Host.LogDriver }}'
|
|
journald
|
|
```
|
|
The **passthrough** driver passes down the standard streams (stdin, stdout, stderr) to the
|
|
container. It is not allowed with the remote Podman client, including Mac and Windows (excluding WSL2) machines, and on a tty, since it is
|
|
vulnerable to attacks via TIOCSTI.
|