-
Notifications
You must be signed in to change notification settings - Fork 107
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Podman container.start(..., attach=True)
does not attach stdout to the terminal.
#550
Comments
I think this PR resolves it but there are failing tests (expecting the alternative behaviour of not seeing stdout?). |
Any updates on this? I'm currently relying on directly using |
It seems there are no recent updates. If you feel up to the task, feel free to continue the PR or open a new one. We'll still credit Lewis for his work on the subject :) |
@gabrieldemarmiesse I think the main open question is whether you're happy for this behaviour change to be made (the failing tests on my PR demonstrate how this is technically a breaking change). |
Sorry, I didn't have my head in the game. I took a look again at the PR. I'll comment there. |
When creating a Podman container and starting with attach, the below does not show any stdout from the container, but input is still connected.
Running the code below will block on
container.start
but not show any output. I can inputexit
and the rest of the process will continue executing.If doing this through the CLI instead, I see the container prompt as expected.
Is this a bug in
container.start
?The text was updated successfully, but these errors were encountered: