Unexpected error forwarding signal on Travis-CI about tini HOT 3 CLOSED

Thanks for the report. I'm looking into this.

Tini does need to be able to pass signals on to its child process. This may be a problem, especially if your child process is running as a different user. I'll try and reproduce your issue.

It looks like start-notebook.sh changes user, so if you're up for it, it might make sense to start Tini itself in start-notebook.sh (in your exec line) to run Tini as the same user as the rest of your stuff.

Cheers,

from tini.

Thanks for the quick feedback. After I filed this, I tracked down travis-ci/travis-ci/issues/4751 which suggests --privileged as a quickfix and makes it look like certain caps limits are being set on travis.

The problem does go away with --privileged so I don't think there's anything wrong here. Will close.

(For the record in case others happen upon this: I switched to not using Docker at all because after fixing the signal issue, I hit other problems with my tornado tests failing mysteriously within the container: https://travis-ci.org/jupyter-incubator/kernel_gateway/builds/85342979 in container vs https://travis-ci.org/jupyter-incubator/kernel_gateway/builds/85345398 outside container.)

from tini.

Thanks for the heads up, @parente.

I'll try and add some documentation explaining the permissions that Tini (or anything that does zombie reaping and signal forwarding, really) needs to run.

Cheers,

from tini.