I agree that supervisor is great running inside containers, but I'm talking about having supervisor run containers themselves. I've been having supervisor run containers for almost 6 months now with no issues; there is nothing fancy about it and it has benefits over other options.
There are a variety of people that are doing this (or want to do this) as well: http://stackoverflow.com/questions/30034813/best-way-to-manage-docker-containers-with-supervisord http://stackoverflow.com/questions/31074492/launching-multiple-docker-containers-with-supervisor http://stackoverflow.com/questions/31197724/shutting-down-docker-containers-via-supervisor There is only one issue (which I described in the original e-mail) that has to do with a corner case of using named containers. My patches add support for Docker directly into the supervisor configuration, which fixes this corner case and helps new users correctly get things working (since there are various Docker flags which must be set correctly for it to work). Cheers, ~Michael On Fri, Apr 29, 2016 at 1:00 PM, < [email protected]> wrote: > Re: [Supervisor-users] Supervisor Support for Docker
_______________________________________________ Supervisor-users mailing list [email protected] https://lists.supervisord.org/mailman/listinfo/supervisor-users
