This is where the main issue is as you may want to restart Monit or upgrade it for an emergency case (because in theory you shouldn’t have to touch processes inside your container and deploy a new container instead that will replace the current one). As said, the first launched command on Docker will take the PID 1. I hope you’re now convinced that Monit is a very good candidate to manage processes inside a Docker container. That mean this entry point should be able to manage boot order, dependencies, retry count, timeout etc…and only Monit is able to do that. In Docker, you really need a featured process manager if you want to run several processes.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |