There is superficial overlap between Docker and traditional process supervisors - both will fork/exec your application, monitor its status, collect logs etc. A

There is superficial overlap between Docker and traditional process supervisors - both will fork/exec your application, monitor its status, collect logs etc. And indeed in a simple test/development setting, you can use Docker without the overhead of installing supervisord, runit, upstart etc. But once you're in production, you typically want to combine the two: a process supervisor to manage the boot process of your machine, auto-restart etc. (typically upstart on Ubuntu, systemd on Red Hat 7+, etc.). In this case, the supervisor simply calls out to docker, which "wraps" your application in a way similar to chroot. I hope this helps.