<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - nspawn catches kill signal only when using jenkins" href="https://bugs.freedesktop.org/show_bug.cgi?id=87732#c3">Comment # 3</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - nspawn catches kill signal only when using jenkins" href="https://bugs.freedesktop.org/show_bug.cgi?id=87732">bug 87732</a> from <a class="email" href="mailto:philantrop@exherbo.org" title="Wulf C. Krueger <philantrop@exherbo.org>"> Wulf C. Krueger</a> <pre>Same issue here. I've tried looking into the Tomcat side of things to make sure it's not Tomcat sending a KILL signal but it definitely isn't. This is what happens here: sudo /usr/bin/linux32 /usr/bin/systemd-nspawn --capability=CAP_MKNOD -D /srv/jenkins/stage_x86 /tmp/make-exherbo-stages Spawning container stage_x86 on /srv/jenkins/stage_x86. Press ^] three times within 1s to kill container. Container stage_x86 terminated by signal KILL. This happens for *every* single job in Jenkins which is a huge problem.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>