Splunk Docker container not trapping SIGTERM or SIGINT
Open
@nwang92 is already working on this.
Since May 12, 2021.
- Dominant language
- Python
- Stars
- 549
- Forks
- 277
- Avg merge
- 3d 9h
- Merged PRs (30d)
- 2
Description
Has anyone experience issues with the trap teardown SIGINT SIGTERM not actually being "trapped"
Using this
docker run --name so1 --hostname so1 -p 8000:8000 \
-e "SPLUNK_PASSWORD=P@ssw0rd!" \
-e "SPLUNK_START_ARGS=--accept-license" \
-d splunk/splunk:latest
If I send docker stop -t 60 so1 or docker kill --signal=SIGTERM so1 the container dies instantly. I would expect the SIGTERM to trigger a splunk stop but that does not happen. This causes concern for data integrity.
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.
Assessment
This issue has not been assessed yet.