0

I cannot find a solution on the net: I automatically (re-) deploy my stack using 

docker stack deploy -c compose.yml atu

but it seems, the service contianers are all killed immediatly, which causes problems, because they cannot shutdown properly / gracefully.

Is there a way to first try stop (SIGTERM 15) the containers that are to be updated?

Best regards

LalaBox
  • 243
  • 2
  • 4
  • 10
  • If you exec into a container and send a sigterm to pid 1, does it exit gracefully? – BMitch Sep 11 '18 at 10:12
  • yes, maually stopping causes the Tomcat to shutdown properly; of course, the service monitorring the stopped container notices the status change and just starts a new Container. It is only a problem using the "docker stack deploy" method since it seems to use kill -9, which does not allow the proper shutdown. I could probably write a script which stops all containers in advance, but then i would always have to stop ALL Services (Containers), even those which would not have been updated due to "no changes"... – LalaBox Sep 12 '18 at 08:57

0 Answers0