-
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
--preserve-fds hangs podman #4020
Comments
Damn. Did we miss this one when we implemented conmon exec? @haircommander |
I thought i implemented it but I forgot to verify it worked |
Regression: this is back. I don't know if it's podman, conmon, runc, or something else:
Bizarrely, I dnf-upgraded the 'works' system to match all the versions in 'hangs' --- and everything still works. I know it's not just my systems because this is causing CI failures Symptom: # podman run --name test1 -d docker.io/library/alpine:latest top
39c9fd570fe7634acfd66140de740472ff611f7d6be6f302927fe38bdfc816ca
# podman exec --preserve-fds 1 test1 date
Sat Mar 28 14:55:36 UTC 2020
[hangs] If I try a |
oddly, the conmon version in that CI run is 2.0.3 (according to the podman info tests), which is really out of date I ran manually, and wasn't able to hit it with conmon 2.0.13 and podman 1.7.0, so I think this has to do with the exec rework and not conmon |
Thanks for looking, @haircommander. I've filed new issue #5666 and will close this one. |
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
Steps to reproduce the issue:
podman run --rm -it --name whatever busybox
New terminal:
podman exec --preserve-fds=1 -ti whatever sh
Describe the results you received:
The podman exec command hangs for about two minutes, then exits with
Error: container creation timeout: internal libpod error
. While exec hangs, the initial session is unresponsive as well, but it resumes afterwards.Describe the results you expected:
podman exec
enters the container without any hangs.Additional information you deem important (e.g. issue happens only occasionally):
I believe this also breaks the container support of Gnome Builder.
Output of
podman version
:Output of
podman info --debug
:Package info (e.g. output of
rpm -q podman
orapt list podman
):Additional environment details (AWS, VirtualBox, physical, etc.):
Fedora Silverblue 30:
The text was updated successfully, but these errors were encountered: