log finish but container still running
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 7.2k
- Forks
- 1.7k
- Avg merge
- 13d 8h
- Merged PRs (30d)
- 2
Description
I use docker-py to run some jobs. After create and start a container using the low-level API, function docker_client.logs(container=container_id, stream=True) used to get the log until the container finish. This always works well. But recently, some containers were still running but the log function had already finished running.
Job in these containers used pytorch and multiprocess. Dose it matter? And what determines the end of log output?
Environment :
ubuntu:16.04
docker: 18.06.0-ce
py-docker: 3.5.0
docker API: v1.35
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 the behavior with the low-level container create/start flow and docker_client.logs(container=container_id, stream=True) under the listed Docker and docker-py versions. Compare log-stream termination with container state while a PyTorch multiprocess job runs; done means the cause and conditions for ending the log output are documented or covered by a regression test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, python
- Domain
- api
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100