-
Notifications
You must be signed in to change notification settings - Fork 3k
podman-remote: kill -s: hangs #7135
Copy link
Copy link
Closed
Labels
kind/bugCategorizes issue or PR as related to a bug.Categorizes issue or PR as related to a bug.locked - please file new issue/PRAssist humans wanting to comment on an old issue or PR with locked comments.Assist humans wanting to comment on an old issue or PR with locked comments.remoteProblem is in podman-remoteProblem is in podman-remote
Description
In window 1:
$ ./bin/podman system service --timeout=0In 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 containerUsing 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.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
kind/bugCategorizes issue or PR as related to a bug.Categorizes issue or PR as related to a bug.locked - please file new issue/PRAssist humans wanting to comment on an old issue or PR with locked comments.Assist humans wanting to comment on an old issue or PR with locked comments.remoteProblem is in podman-remoteProblem is in podman-remote