-
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-remote mangles SIGINT #5004
Comments
@vrothberg PTAL |
I have moved this to crun -> containers/crun#230 closing for now |
I've changed crun to force the default for the signal handlers and behave like runc. But I think it is safer anyway to do: Note the extra |
Good idea, thx. |
Recommended as part of: containers#5004 and containers/crun#230 Signed-off-by: Chris Evich <[email protected]>
Recommended as part of: containers#5004 and containers/crun#230 Signed-off-by: Chris Evich <[email protected]>
- images test: add test for 'table' and '\t' formatting - image mount test: check output from 'umount', test repeat umount (NOP), and test invalid-umount - kill test: remove kludgy workaround for crun signal bug ref: containers#5004 -- code is no longer needed (fingers crossed), and the workaround involved pulling an expensive image. - selinux test: add new tests for shared context in: * pods , w/ and w/o infra container (ref: containers#7902) * containers with namespace sharing: --ipc, --pid, --net - selinux test: new test for --pid=host (disabled pending propagation of container-selinux-2.146, ref: containers#7939) Signed-off-by: Ed Santiago <[email protected]>
/kind bug
Description
Discovered in master, sometime prior to commit a8bd347 under F31, the system-tests fail in
130-kill.bats
.Steps to reproduce the issue:
From a clone of the repo. run 'make remotesystem' (observe test failure)
Copy attached script into root of source tree, rename and execute it.
repro.sh.txt
Describe the results you received:
Describe the results you expected:
Running 'make remotesystem' should pass.
Additional information you deem important (e.g. issue happens only occasionally):
Unsure if munging of signal 2 is intended or not, guess that it is.
Output of
podman version
:Output of
podman info --debug
:Additional environment details (AWS, VirtualBox, physical, etc.):
Was running as the local user "foobar". Problem does not reproduce under F30.
The text was updated successfully, but these errors were encountered: