Some more links Huang: Docker has its own issues - depending on what is the docker entrypoint you use, you can get different (and wrong) behaviour. It is especially problematic if you are using bash script as an entrypoint. It can lead to zombie processes easily.
There are many blogs about it, but I think one of the best explanations can be found here (https://github.com/krallin/tini/issues/8) What is the most important though that as of Docker 1.13 you can use --init flag when starting docker and it will run the "tini" init process for you that takes care about reaping all the docker processes. See: https://github.com/krallin/tini#using-tini for details. J. On Sat, Jan 4, 2020 at 9:20 PM Huang Xinbin <[email protected]> wrote: > +1 for the `stop` idea too. In my team, we use docker to manage airflow, so > `stoping` and `restart on failure` are all handled by Docker. It works > great so far, but not sure if this is a good practice and I would > definitely like to hear other people's feedback. > > i.e. thanks Jarek for the reference links, will take a deeper look into > those. > > Best > Bin > > > On Sat, Jan 4, 2020 at 6:59 AM hotmail <[email protected]> wrote: > > > +1 for `stop` arg, and thank Jarek for the clarification. > > > > Best Wish > > — Jiajie > > > > > -- Jarek Potiuk Polidea <https://www.polidea.com/> | Principal Software Engineer M: +48 660 796 129 <+48660796129> [image: Polidea] <https://www.polidea.com/>
