doc: explain --interactive in more detail

Clarifies the behavior of --interactive in both attached and unattached
scenarios.

Adds a caveat and explanation for --interactive being hungry as
described in https://github.com/containers/podman/issues/24370.

Signed-off-by: Alicia Boya García <aboya@igalia.com>
This commit is contained in:
Alicia Boya García
2024-10-31 14:05:10 +01:00
parent 2da21d1524
commit 37c8e10031
4 changed files with 8 additions and 4 deletions

View File

@ -4,4 +4,8 @@
####> are applicable to all of those.
#### **--interactive**, **-i**
When set to **true**, keep stdin open even if not attached. The default is **false**.
When set to **true**, make stdin available to the contained process. If **false**, the stdin of the contained process is empty and immediately closed.
If attached, stdin is piped to the contained process. If detached, reading stdin will block until later attached.
**Caveat:** Podman will consume input from stdin as soon as it becomes available, even if the contained process doesn't request it.