From 41d169d211d44eb49c1d678a52ecbe721d8480c5 Mon Sep 17 00:00:00 2001 From: Chris Vermilion Date: Sat, 3 Apr 2021 17:13:01 -0400 Subject: [PATCH] Update stop.md Updates the stop.md doc to mention that the stop signal can be changed, either with the Dockerfile or via `docker run --stop-signal`. This is a real gotcha if you're not familiar with this feature and build a container that extends a container that uses `STOPSIGNAL`. Signed-off-by: Christopher Vermilion --- docs/reference/commandline/stop.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/reference/commandline/stop.md b/docs/reference/commandline/stop.md index e4c567fb78..282a378582 100644 --- a/docs/reference/commandline/stop.md +++ b/docs/reference/commandline/stop.md @@ -19,7 +19,9 @@ Options: ## Description The main process inside the container will receive `SIGTERM`, and after a grace -period, `SIGKILL`. +period, `SIGKILL`. The first signal can be changed with the `STOPSIGNAL` +instruction in the container's Dockerfile, or the `--stop-signal` option to +`docker run`. ## Examples