cron.sh doesn't stop without SIGKILL
Open
Beginner friendly
Nobody has claimed this yet.
1. To develop
bug
feature: cron
image
- Dominant language
- Shell
- Stars
- 7.4k
- Forks
- 1.9k
- PR merge metrics
- No merged PRs in 30d
Description
The cron.sh script doesn't stop with the default SIGWINCH signal (or SIGTERM), which causes docker stop to wait for 10 seconds and fail over to SIGKILL. To reproduce:
docker run --name nextcloud-cron --rm --entrypoint /cron.sh docker.io/library/nextcloud
docker stop nextcloud-cron # Takes 10 seconds to complete
Docker hides this by silently falling back to SIGKILL, but it makes stopping take an unnecessary 10 seconds. If using podman, podman stop nextcloud-cron returns
WARN[0010] StopSignal SIGWINCH failed to stop container nextcloud-cron in 10 seconds, resorting to SIGKILL
Contributor 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.
Research direction
Start with the cron.sh script used by the Docker image and reproduce the issue with the provided docker run and docker stop commands. Trace how the script handles the default stop signals, then verify that the container stops without waiting for the timeout or requiring SIGKILL.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, shell
- Domain
- devops
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 68/100