APIClient.exec_start close connection problem
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 7.2k
- Forks
- 1.7k
- Avg merge
- 13d 8h
- Merged PRs (30d)
- 2
Description
My system is Cenots7, docker-py version 2.5.1, docker server version 1.12.6 (yum install form epel)
cli = APIClient(base_url='127.0.0.1:2375', version='auto')
task = ctr.exec_create('container_name', 'date')
ctr.exec_start(task['Id'])
When i run above code, netstat -ant|grep 2375 output connection state is CLOSE_WAIT and FIN_WAIT2
Is it right?
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
Reproduce the reported APIClient.exec_start call on the stated CentOS 7, docker-py 2.5.1, and Docker 1.12.6 setup, then inspect the exec_start connection handling. Check whether CLOSE_WAIT and FIN_WAIT2 remain after the command completes and compare the behavior with the expected connection lifecycle. Done means determining whether the states are expected or identifying a reproducible connection-closing failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, python
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100