Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docker kill: don't set default signal on the client side #3271

Merged
merged 1 commit into from
May 13, 2022

Conversation

thaJeztah
Copy link
Member

@thaJeztah thaJeztah commented Aug 25, 2021

The default signal is already determined by the daemon, so the CLI should not send a signal.

- Description for the changelog

- A picture of a cute animal (not mandatory but encouraged)

@codecov-commenter
Copy link

Codecov Report

Merging #3271 (711e6b4) into master (ae3b0b3) will not change coverage.
The diff coverage is 0.00%.

@@           Coverage Diff           @@
##           master    #3271   +/-   ##
=======================================
  Coverage   58.24%   58.24%           
=======================================
  Files         287      287           
  Lines       24155    24155           
=======================================
  Hits        14070    14070           
  Misses       9225     9225           
  Partials      860      860           

@thaJeztah thaJeztah changed the title docker kill: use "SIGKILL" instead of "KILL" as default signal docker kill: don't set default signal on the client side May 13, 2022
The default signal is already determined by the daemon, so the
CLI should not send a signal.

Signed-off-by: Sebastiaan van Stijn <[email protected]>
@thaJeztah thaJeztah merged commit 55de347 into docker:master May 13, 2022
@thaJeztah thaJeztah deleted the kill_canonical_signal_name branch May 13, 2022 09:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants