New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docker logs change tail default #40452
Comments
This would have to be implemented in the cli (github.com/docker/cli). While I understand the request, my concern is that changing the behaviour would likely be a breaking change (the behaviour has been like this for a long time ( @cpuguy83 wdyt? |
Current default is indeed silly, just that it's had a long long history. Alternatively we could do something like what journalctl does and essentially pipe it through |
We could also enforce a default max size so we don't spew gobs and gobs of logs. |
should the default driver be the |
Oh I was thinking max read size more than max store size. |
Great to read that this query is nicely welcomed. I understand the backward-compatibility concern and can't tell how painful this could be to some users. 🤞 so that an acceptable solution is found. |
+1 Usually I give it an alias
|
@thaJeztah I've faced similar issue while using docker logs command. Sometimes it makes the debugging hard in Dev environments because debug logs are also enabled. I've completed the Dev environment setup of the moby package. I'd love to discuss the solution and contribute. Could you please assign this issue to me. Thanks. |
outputs the whole container history, which is non-sense for a container that has been alive for some time.
Hence as far as I'm concerned, I always have type
docker logs --tail=100 -f <container_name>
which is crazy long for something that feels like a default behavior.Whichever value different than
all
would work for me: eg. 10 ou 100.But who wants to output 10k lines by default and block the process for 2/3mins?
The text was updated successfully, but these errors were encountered: