-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Don't use supervisor as the init process #24
Comments
Hey there, I apologize for the shameless plug, but I noticed you were considering using I happen to have written a tool just for that. It's called If you're curious; you can find it here on Github: https://github.com/krallin/tini |
I love the name already, 'tini' ! On 10 September 2015 at 19:45, Thomas Orozco notifications@github.com
|
@krallin thanks for sharing! I will definitely look into it. |
Started a branch with tini replacing supervisord. Works as advertised. I need to beat up each image a bit more to ensure there's no surprises. One point worth clarifying: we're still going to have to set tini to run as root in the images, not because it needs to do so but because our start-notebook.sh script supports options that require root privileges, namely the jovyan UID switch and granting sudo. |
Sounds cool. I've been trying out tini, as well. I'd be curious to know what you find out from your stress tests, @parente. |
See jupyter/notebook#334 (comment) for background.
Possible fixes ...
Switch to phusion/baseimage. Concern: size and change of OS.
Use runit like phusion/baseimage does (http://www.sourcediver.org/blog/2014/11/17/using-runit-in-a-docker-container/). Concern: env var workaround described therein.
Port phusion/baseimage to debian. Concern: yet another thing to maintain.
Wait for docker to give reaping "for free" (Evented Process Monitor moby/moby#11529).
The text was updated successfully, but these errors were encountered: