mirror of
https://github.com/containers/podman.git
synced 2025-08-24 18:12:25 +08:00
950f612b56
it works in a similar way to passthrough but it allows to be used also on a TTY. conmon support: https://github.com/containers/conmon/pull/465 Closes: https://github.com/containers/podman/issues/20767 Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
19 lines
971 B
Markdown
19 lines
971 B
Markdown
####> This option file is used in:
|
|
####> podman create, run
|
|
####> If file is edited, make sure the changes
|
|
####> are applicable to all of those.
|
|
#### **--log-driver**=*driver*
|
|
|
|
Logging driver for the container. Currently available options are **k8s-file**, **journald**, **none**, **passthrough** and **passthrough-tty**, with **json-file** aliased to **k8s-file** for scripting compatibility. (Default **journald**).
|
|
|
|
The podman info command below displays 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.
|
|
|
|
The **passthrough-tty** driver is the same as **passthrough** except that it also allows it to be used on a TTY if the user really wants it.
|