output hanging #236
Comments
|
@giuseppe can you PTAL |
|
caused by 6287bd8, see my investigation here reverting it (applies cleanly) fixes the issue entirely |
giuseppe
added a commit
to giuseppe/conmon
that referenced
this issue
Feb 2, 2021
commit 6287bd8 introduced the regression. writes to the attached sockets must be blocking, otherwise the write_back_to_remote_consoles() shutdowns the socket when write fails with EAGAIN. I've verified the original issue fixed with commit 62887bd is not reintroduced with this patch. Closes: containers#236 Signed-off-by: Giuseppe Scrivano <[email protected]>
|
this part of the code is a mess :( Opened a PR: #237 |
haircommander
pushed a commit
that referenced
this issue
Feb 2, 2021
commit 6287bd8 introduced the regression. writes to the attached sockets must be blocking, otherwise the write_back_to_remote_consoles() shutdowns the socket when write fails with EAGAIN. I've verified the original issue fixed with commit 62887bd is not reintroduced with this patch. Closes: #236 Signed-off-by: Giuseppe Scrivano <[email protected]>
|
I will try your fix later tonight! edit: confirming it works now |
|
Just tried with 2.0.26 today and it works! Thank you :) |
apyrgio
pushed a commit
to freedomofpress/maint-dangerzone-conmon
that referenced
this issue
Jan 24, 2024
Closes: containers#236 Closes: #1014030
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
Since after version 2.0.22 a large amount of data in stdout/stderr hangs the output and all I can do is ctrl+c and podman kill the container.
Here's how to reproduce:
podman run -rm -ti alpineOnce in the shell:
find /I also encountered issues with vscode trying to reconnect to a container (it might be related) and failing a lot.
The same steps with 2.0.22 work just fine.
I investigated a little but couldn't find anything, sorry. Might it be related to 0f092d5?
The text was updated successfully, but these errors were encountered: