Skip to content
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-remote: kill -s: hangs #7135

Closed
edsantiago opened this issue Jul 29, 2020 · 4 comments · Fixed by #7572
Closed

podman-remote: kill -s: hangs #7135

edsantiago opened this issue Jul 29, 2020 · 4 comments · Fixed by #7572
Assignees
Labels
kind/bug Categorizes issue or PR as related to a bug. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. remote Problem is in podman-remote

Comments

@edsantiago
Copy link
Member

In window 1:

$ ./bin/podman system service --timeout=0

In window 2:

$ ./bin/podman pull fedora-minimal

$ ./bin/podman-remote run -d --name foo fedora-minimal env --default-signal sh -c "trap 'echo GOT HERE' 2;while :;do sleep 1;done"
ddd0303f467f170f46ca92e9b8c8b7ce61ca5574ad50de42ea82c4ee2a831cfa

$ time ./bin/podman-remote kill -s 2 foo
^C     <--- I got impatient before waiting 10 minutes
./bin/podman-remote kill -s 2 foo  0.12s user 0.09s system 0% cpu 8:34.25 total

$ ./bin/podman-remote logs foo
GOT HERE           <--- ok, so the signal DID make it to container

Using fedora-minimal and env because of #5004.

It also hangs with -s 3, which indicates that trap is not the problem. It also hangs with just plain sleep 999, I just did the trap thing so I could see if the container was getting the signal.

@edsantiago edsantiago added kind/bug Categorizes issue or PR as related to a bug. remote Problem is in podman-remote labels Jul 29, 2020
@github-actions
Copy link

A friendly reminder that this issue had no activity for 30 days.

@edsantiago
Copy link
Member Author

Still happening, master @ 575b3a3

@vrothberg vrothberg self-assigned this Sep 9, 2020
@vrothberg
Copy link
Member

I'll take a stab at this one. Thanks for providing a reproducer, @edsantiago !

@vrothberg
Copy link
Member

#7572 to the rescue

vrothberg added a commit to vrothberg/libpod that referenced this issue Sep 9, 2020
Invert the branch logic to match the comment.  Docker seems to wait for
the container while Podman does not.

Enable the remote-disabled system test as well.

Fixes: containers#7135
Signed-off-by: Valentin Rothberg <[email protected]>
@github-actions github-actions bot added the locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. label Sep 22, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 22, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
kind/bug Categorizes issue or PR as related to a bug. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. remote Problem is in podman-remote
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants