Open jhc4318 opened 7 months ago
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 subprocess
given the difference in behaviour.
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
?