-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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 hangs on "receiving" too much output to console #9183
Comments
@vrothberg This reminds me of #9096 but in the other direction. Likely related. |
That's interesting. I agree it's very likely the same issue. Should clarify my original report that the hanging at prompt occurs when using pod with an interactive command, otherwise it just returns with truncated, as the other bug report says, output. Likely the hanging behavior is a result of some part of the interactive prompt bit of podman not knowing what to do when the container process aborts abruptly. I can help debug, I'm pretty handy with git bisect. Give me some pointers which of the components of podman is the likely culprit EDIT: this regressed some time after conmon 2.0.22 and before 2.0.24 - when I rolled back to that version, I no longer get the issue, when I try with 2.0.24 I do get the issue. Couldn't try 2.0.23, immediately got an EOF error on that version |
Thanks a bunch - Conmon doesn't get much activity, so that should narrow things down to a narrow set of commits. @haircommander PTAL |
|
@giuseppe PTAL Thanks everybody! |
closing as a duplicate of containers/conmon#236 |
/kind bug
Description
Executions in containers hang when they output too much data too fast to stdout.
Steps to reproduce the issue:
podman run docker.io/archlinux hexdump -C /dev/random
Describe the results you received:
execution hangs and ends at around 20k of the file hexdumped
Describe the results you expected:
execution should output the entire hexadecimal representation of the C library binary (200k file roughly)
Additional information you deem important (e.g. issue happens only occasionally):
not specific to hexdump by the way, anything triggers the hangs. even cat-ing a large file. actually first noticed it when running "pacman -Qi" (prints all package info verbosely on archlinux)
Output of
podman version
:Output of
podman info --debug
:Package info (e.g. output of
rpm -q podman
orapt list podman
):Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide?
Yes
Additional environment details (AWS, VirtualBox, physical, etc.):
physical
The text was updated successfully, but these errors were encountered: