Closed cevich closed 4 years ago
@vrothberg PTAL
I have moved this to crun -> https://github.com/containers/crun/issues/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: ./bin/podman-remote run -d --name=foobar fedora-minimal env --default-signal sh -c "for i in ${signals[*]}; do trap \"echo got: \$i\" \$i; done; echo READY; while ! test -e /stop; do sleep 0.05; done;echo DONE"
Note the extra env --default-signal
Note the extra env --default-signal
Good idea, thx.
/kind bug
Description
Discovered in master, sometime prior to commit a8bd3473e0bb648be88b6d9b84f18fc097de70ee 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.