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

Stop dockerd nicely #96

Merged
merged 1 commit into from
Apr 11, 2024
Merged

Stop dockerd nicely #96

merged 1 commit into from
Apr 11, 2024

Conversation

github-actions[bot]
Copy link
Contributor

This is an automatic cherry-pick of d7a2fdbd3a261e7e7880fd418f698ebf46df5a0a

The original PR was #185 with message:

Stop dockerd by sending SIGTERM and if it fails to terminate, send SIGKILL after 20 seconds.

When all containers stop quickly, dockerd will stop in just 1 second. If one or more containers refuse to stop, dockerd will send SIGKILL after 10 seconds, meaning dockerd will take 11 or 12 seconds to stop.

The old behavior was to always wait 10 seconds, then send SIGTERM, but the intention was the behavior described above, save for a too short SIGKILL delay.

Checklist before requesting a review

  • I have performed a self-review of my own code
  • I have verified that the code builds perfectly fine on my local system
  • I have added tests that prove my fix is effective or that my feature works
  • I have commented my code, particularly in hard-to-understand areas
  • I have verified that my code follows the style already available in the repository
  • I have made corresponding changes to the documentation

Stop dockerd by sending SIGTERM and if it fails to terminate,
send SIGKILL after 20 seconds.

When all containers stop quickly, dockerd will stop in just 1 second.
If one or more containers refuse to stop, dockerd will send SIGKILL
after 10 seconds, meaning dockerd will take 11 or 12 seconds to stop.

The old behavior was to always wait 10 seconds, then send SIGTERM,
but the intention was the behavior described above, save for a too
short SIGKILL delay.
@github-actions github-actions bot requested a review from a team as a code owner April 10, 2024 06:37
@killenheladagen killenheladagen merged commit ca25e8f into main Apr 11, 2024
@killenheladagen killenheladagen deleted the cherrybot-25021 branch April 11, 2024 06:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

1 participant