Q: containter.logs follow vs stream ? non-blocking logs ?

[vitalik]

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 ?

[shin-]

follow keeps the connection alive to stream future logs.

Use co-routines or threads to handle multiple streams at once. See e.g. https://github.com/docker/compose/blob/master/compose/cli/log_printer.py

[SamuelM333]

@vitalik I have a working version for live logs in a web app that I developed for monitoring and Docker services. See here https://github.com/SamuelM333/flying-whales/blob/live-logs/app.py#L111

The background task is started by SocketIO but the idea is the same. Use threads to avoid the blocking operations.