3 ms·
Whats advantage of having a "supervisor" inside the container, rather than just "supervising" the container itself?
by nemothekid 11y ago
Whats advantage of having a "supervisor" inside the container, rather than just "supervising" the container itself?
- sandGorgon 11y agomaybe you should read this [1]. We have always run all processes under a supervisor. [1] https://blog.phusion.nl/2015/01/20/docker-and-the-pid-1-zombie-reaping-problem/ https://blog.phusion.nl/2015/01/20/docker-and-the-pid-1-zomb...
- ymt123 11y agoI think this was the problem [1] was targeting [1] http://engineeringblog.yelp.com/2016/01/dumb-init-an-init-for-docker.html http://engineeringblog.yelp.com/2016/01/dumb-init-an-init-fo...
- sandGorgon 11y agoOne of many. Which is why u think might as well get systemd working on docker...
- nemothekid 11y agoI see, so it looks like if your process spawns other processes and doesn't reap them when they die, you end up in trouble with zombie processes in docker.
- cyphar 11y agoBecause "only one process in a container" is a dangerous rule (because it has so many exceptions). In certain cases, that idea makes sense, but you shouldn't contort your app such that you only have one process in every container. Not to mention that there are other issues (PID 1 has unique problems that databases and your app aren't used to having to deal with).