From dc8d7ad23d3610439e3f8b594ed01aae9a58b21a Mon Sep 17 00:00:00 2001 From: Hynek Schlawack Date: Sat, 17 Jun 2017 10:17:48 +0200 Subject: [PATCH] STOPSIGNAL --- .../update-strategies/handling-signals.html.md | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/website/source/docs/operating-a-job/update-strategies/handling-signals.html.md b/website/source/docs/operating-a-job/update-strategies/handling-signals.html.md index 8fbcf8d29..4490da0c5 100644 --- a/website/source/docs/operating-a-job/update-strategies/handling-signals.html.md +++ b/website/source/docs/operating-a-job/update-strategies/handling-signals.html.md @@ -36,7 +36,9 @@ job "docs" { } ``` -Please note that the behavior is subtly different for Docker-based tasks. In -this case a `docker stop` command is issued that will send a `SIGTERM` to your -container entry point instead. The `kill_timeout` option is still respected -though. +The behavior is slightly different for Docker-based tasks. Nomad will run the +`docker stop` command with the specified `kill_timeout`. The signal that `docker +stop` sends to your container entrypoint is configurable using the +[`STOPSIGNAL` configuration directive] +(https://docs.docker.com/engine/reference/builder/#stopsignal), however please +note that the default is `SIGTERM`.