Hi Bert and Nick, Docker will issue a SIGTERM, and assumes an app responds to that. It is up to the container to “do what’s needed” upon receiving a SIGTERM. So it’s best practice to make sure SIGTERM does the right thing…. When using Docker, you should expect your container to be started, stopped, restarted elsewhere etc.
Nick: As Brian said: use tini either in your Dockerfile, or when starting the container by using the --init parameter… Frank > On 13 Jan 2019, at 21:48, bert hubert <[email protected]> wrote: > > On Sun, Jan 13, 2019 at 08:32:33PM +0000, Brian Candler wrote: >>> sends a `SIGTERM` to PID 1, waits some amount of time, and then sends >>> SIGKILL to force it to stop. It’s having to resort to SIGKILL, because >>> `pdns_server` doesn’t respond to `SIGTERM`. What is the correct signal to >>> tell PDNS to shut down? > >> The problem is not with pdns, it's with docker: strange things happen if you >> run the application as pid 1. For an explanation see: >> https://hackernoon.com/my-process-became-pid-1-and-now-signals-behave-strangely-b05c52cc551c > > In addition, you could ask powerdns to stop using pdns_control. > > Bert > _______________________________________________ > Pdns-users mailing list > [email protected] > https://mailman.powerdns.com/mailman/listinfo/pdns-users _______________________________________________ Pdns-users mailing list [email protected] https://mailman.powerdns.com/mailman/listinfo/pdns-users
