From 580312e771f979b9c3b0f763f6ff63fa2a0f59b7 Mon Sep 17 00:00:00 2001 From: Marcel Partap Date: Mon, 4 Mar 2019 17:29:31 +0100 Subject: [PATCH] stop_signal supported with docker stack deploy support was added nearly two years ago, c.f. https://github.com/docker/cli/issues/370 --- compose/compose-file/index.md | 5 ----- 1 file changed, 5 deletions(-) diff --git a/compose/compose-file/index.md b/compose/compose-file/index.md index 4a736aaaa29..f25ec8436d2 100644 --- a/compose/compose-file/index.md +++ b/compose/compose-file/index.md @@ -857,7 +857,6 @@ The following sub-options (supported for `docker-compose up` and `docker-compose - [network_mode](#network_mode) - [restart](#restart) - [security_opt](#security_opt) -- [stop_signal](#stop_signal) - [sysctls](#sysctls) - [userns_mode](#userns_mode) @@ -1616,10 +1615,6 @@ SIGTERM. Setting an alternative signal using `stop_signal` causes stop_signal: SIGUSR1 -> **Note**: This option is ignored when -> [deploying a stack in swarm mode](/engine/reference/commandline/stack_deploy.md) -> with a (version 3) Compose file. - ### sysctls Kernel parameters to set in the container. You can use either an array or a