container.stop() behaves in an unexpected manner
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 7.2k
- Forks
- 1.7k
- Avg merge
- 13d 8h
- Merged PRs (30d)
- 2
Description
If I do not provide a timeout, it seems to instantly kill the container, even explicitly setting stop_signal to SIGTERM. I think there is a bug which makes the timeout 0. My current workaround is to simply provide the argument timeout=10
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 by reproducing container.stop() without a timeout while explicitly setting stop_signal to SIGTERM, then compare it with timeout=10. Trace how the Python client passes the omitted timeout to the Docker Engine API; done means the default behavior no longer immediately kills the container and matches the documented stop semantics.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, python
- Domain
- api
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100