Q: containter.logs follow vs stream ? non-blocking logs ?
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 7.2k
- Forks
- 1.7k
- Avg merge
- 13d 8h
- Merged PRs (30d)
- 2
Description
I think documentation does not really explain the follow argument in container.log function...
what does it do ?
and second question - is there a way to get logs(..., stream=True) to be non blocking ?
What I'm trying to achieve: I have 10+ containers running and they write time to time some data to stdout...
I want to make a script that periodically pulls latest logs for each of them...
but container.log(stream=True) is blocked until a line appears in stdout..
is there a way to make it non-blocking ?
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 container.log entry point and the follow and stream=True arguments described in the issue. Clarify what follow does and determine whether streamed logs can be consumed non-blockingly for periodic polling. Done means the documentation answers both questions and accurately describes the observed behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, python
- Domain
- api, documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100