mirror of https://github.com/docker/cli.git
docker kill: don't set default signal on the client side
The default signal is already determined by the daemon, so the CLI should not send a signal. Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
This commit is contained in:
parent
1b922a47c1
commit
20138a81bc
|
@ -34,7 +34,7 @@ func NewKillCommand(dockerCli command.Cli) *cobra.Command {
|
||||||
}
|
}
|
||||||
|
|
||||||
flags := cmd.Flags()
|
flags := cmd.Flags()
|
||||||
flags.StringVarP(&opts.signal, "signal", "s", "KILL", "Signal to send to the container")
|
flags.StringVarP(&opts.signal, "signal", "s", "", "Signal to send to the container")
|
||||||
return cmd
|
return cmd
|
||||||
}
|
}
|
||||||
|
|
||||||
|
|
|
@ -13,7 +13,7 @@ Kill one or more running containers
|
||||||
|
|
||||||
Options:
|
Options:
|
||||||
--help Print usage
|
--help Print usage
|
||||||
-s, --signal string Signal to send to the container (default "KILL")
|
-s, --signal string Signal to send to the container
|
||||||
```
|
```
|
||||||
|
|
||||||
## Description
|
## Description
|
||||||
|
|
|
@ -1,2 +1,20 @@
|
||||||
The main process inside each container specified will be sent SIGKILL,
|
The `docker kill` subcommand kills one or more containers. The main process
|
||||||
or any signal specified with option --signal.
|
inside the container is sent `SIGKILL` signal (default), or the signal that is
|
||||||
|
specified with the `--signal` option. You can reference a container by its
|
||||||
|
ID, ID-prefix, or name.
|
||||||
|
|
||||||
|
The `--signal` flag sets the system call signal that is sent to the container.
|
||||||
|
This signal can be a signal name in the format `SIG<NAME>`, for instance `SIGINT`,
|
||||||
|
or an unsigned number that matches a position in the kernel's syscall table,
|
||||||
|
for instance `2`.
|
||||||
|
|
||||||
|
While the default (`SIGKILL`) signal will terminate the container, the signal
|
||||||
|
set through `--signal` may be non-terminal, depending on the container's main
|
||||||
|
process. For example, the `SIGHUP` signal in most cases will be non-terminal,
|
||||||
|
and the container will continue running after receiving the signal.
|
||||||
|
|
||||||
|
> **Note**
|
||||||
|
>
|
||||||
|
> `ENTRYPOINT` and `CMD` in the *shell* form run as a child process of
|
||||||
|
> `/bin/sh -c`, which does not pass signals. This means that the executable is
|
||||||
|
> not the container’s PID 1 and does not receive Unix signals.
|
||||||
|
|
Loading…
Reference in New Issue