5 ms·

Why write your own mini-init instead of using something like supervisord?

• masklinn 12y ago
  Supervisord is not an init and must not be run as pid1, that's explicitly mentioned in its documentation[0]: > It shares some of the same goals of programs like launchd, daemontools, and runit. Unlike some of these programs, it is not meant to be run as a substitute for init as “process id 1”. There are micro-inits you could use instead though, s6 should be runnable as pid1 for instance. [0] http://supervisord.org/index.html?highlight=init http://supervisord.org/index.html?highlight=init
  • emeraldd 12y ago
    I'm a little confused here. Especially considering that the docker site lists supervisord explicitly with instructions on how to use it .... see: https://docs.docker.com/articles/using_supervisord/ https://docs.docker.com/articles/using_supervisord/
    • masklinn 12y ago
      There's no problem with running supervisord, inside or outside of docker, there's a problem running supervisord as an init (pid1). You can run openrc or systemd or s6 or runit or minit or whatever and use supervisord on top of that, you just shouldn't use supervisord directly as pid1.
• deleted 12y ago
  [deleted]