Confirm we are correctly handling termination signals like SIGTERM
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 43/100
Research direction
Start by locating how 8Knot handles process signals and shutdown, then trace the path used when Podman sends SIGTERM. Check whether the process completes a graceful shutdown before the runtime timeout; done means SIGTERM is handled and shutdown no longer requires SIGKILL in this scenario.
Written by the indexing model from the issue text.
Description
i see this when ctrl-c ing 8knot in podman:
WARN[0010] StopSignal SIGTERM failed to stop container 8knot_redis-users_1 in 10 seconds, resorting to SIGKILL
Augur has a similar issue where its not listening to the SIGTERM (polite shutdown request) signal from linux, causing the container runtimes timeout to be hit and for it to be sent the SIGKILL (the process is being terminated) signal.
We should check how we handle these signals and make sure it can handle both so that things are shut down gracefully more often.
- Dominant language
- Python
- Stars
- 80
- Forks
- 92
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 13
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from chaoss/8Knot
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 83/100
chaoss/8Knot#1188 · 1 comment ·
Maintainers usually reply within 1 day
-
add CONTRIBUTING.mdOpendocumentation
Difficulty 1/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 58/100
chaoss/8Knot#1241 · 1 reaction ·
Maintainers usually reply within 1 day
-
update references from eightknot.osci.io to eightknot.ioPossibly taken @MoralCode claimed this 5 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
Maintainers usually reply within 1 day
Similar issues
-
integration: media_player
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
home-assistant/core#193344 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
daniel-ospina/tortoise#13607 ·
Maintainers usually reply within 1 day
-
documentation priority: medium
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 66/100
Robin-IA/Congressional-Letters-Dev#1347 ·
Maintainers usually reply within 1 day