Skip to content

Only forward stdin to containers during run and exec commands - #1540

Open
mokibit wants to merge 3 commits into
containers:mainfrom
mokibit:stdin-only-for-run-exec
Open

Only forward stdin to containers during run and exec commands#1540
mokibit wants to merge 3 commits into
containers:mainfrom
mokibit:stdin-only-for-run-exec

Conversation

@mokibit

@mokibit mokibit commented Aug 14, 2026

Copy link
Copy Markdown
Collaborator

podman-compose was incorrectly forwarding its own stdin to all podman subprocesses, including containers started via up. Now only run and exec commands can read stdin, matching docker-compose behavior.
Missing stdin tests were added.

For more on docker-compose up not being interactive, see this discussion:
docker/compose#3081

Fixes #385.

Podman-compose was incorrectly forwarding its own stdin to all podman
subprocesses, including containers started via `up`.

Now only `run` and `exec` commands can read stdin, matching
docker-compose behavior.

Signed-off-by: Monika Kairaityte <monika@kibit.lt>
It allows the stdin behavior integration tests to pipe data into
podman-compose subprocesses.

Signed-off-by: Monika Kairaityte <monika@kibit.lt>
Signed-off-by: Monika Kairaityte <monika@kibit.lt>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

"podman-compose up" does take a stdin

1 participant