if i create a container with fig and let it run and produce lots and lots of logs, when i execute:
fig logs
for the first time it can take minutes to print all the logs (this is because I am running some development application in debug mode). I would like to have a feature like with tail, where I can specify the initial amount of lines say for example:
fig logs -n 1000
which would print the last 1000 lines of the logs it could be either the last for each container or the total 1000, as long i can avoid the initial print of thousands of logs... that I am not interested in...
pmlopes
All 30 comments
AFAIK this is something that's needed upstream in Docker.
bfirsh
on 24 Jun 2014
ok then!
pmlopes
on 26 Jun 2014
@bfirsh
docker now support limit logs
docker logs --help
Usage: docker logs CONTAINER
Fetch the logs of a container
-f, --follow=false Follow log output
-t, --timestamps=false Show timestamps
--tail="all" Output the specified number of lines at the end of logs (defaults to all logs)
ilovenwd
on 3 Aug 2014
Great! We need an implementation of --tail for fig logs then.
bfirsh
on 4 Aug 2014
:+1: +1 yeah
gastonmorixe
on 12 Nov 2014
Please?
gastonmorixe
on 27 Jan 2015
Bump :)
gastonmorixe
on 28 Feb 2015
:+1:
clifton
on 3 Apr 2015
There currently work in progress upstream in Docker to add support for limiting logs; https://github.com/docker/docker/pull/11485
thaJeztah
on 4 Apr 2015
+1 Really need it
mnuessler
on 19 Jun 2015
+1
thiago
on 28 Jul 2015
+1
isuvorov
on 6 Aug 2015
FWIW: +1
abesto
on 7 Aug 2015
+1
ahmadnazir
on 10 Aug 2015
docker-compose rm
docker-compose up
that's will do the trick for you, guys
twistsm
on 14 Aug 2015
This would involve using the logs endpoint in docker-compose logs, as opposed to the attach endpoint, but I think that's fine.
It would also only work for containers using the json-file logging driver, according to the API docs.
aanand
on 17 Aug 2015
@twistsm docker-compose rm && docker-compose up drops volumes (including volumes for data containers), limiting the utility of this workaround :(
abesto
on 26 Aug 2015
:+1: for this.
hSATAC
on 1 Sep 2015
It can solved easy with a bash script like this
docker-compose ps | \
awk '{print $1}' | \
grep APPNAME!! | \
xargs -I{} docker logs --tail=10 -f {}
kevinsimper
on 18 Sep 2015
+1 for this
quantverse
on 30 Nov 2015
+1
lillesvin
on 22 Dec 2015
+1
ezeql
on 21 Jan 2016
+1
koliyo
on 5 Feb 2016
+1
snario
on 12 Feb 2016
+1
gtron
on 15 Feb 2016
+1
krasinski
on 16 Feb 2016
+1
sukrit007
on 16 Feb 2016
This issue makes docker-compose logs useless if you have to wait through 30 minutes of old logs to see what's actually going wrong. Is there a way to clear the logs daemon (or however it is implemented)? Without having to stop all services, rm and the up...
erkie
on 18 Feb 2016
Suggestion:
if -f is specified, automatically default to the last 10 lines.
Follows the usage of the tail command.
Joshfindit
on 24 Jan 2017
if i wanted to just tail from end of the log, is it this?
docker-compose logs -f --tail=1
jaequery
on 2 Aug 2018
Related issues
saulshanabrook
路
3Comments
maltefiala
路
3Comments
Hendrik-H
路
3Comments
guycalledseven
路
3Comments
giggio
路
3Comments
Most helpful comment
Suggestion:
if
-fis specified, automatically default to the last 10 lines.Follows the usage of the
tailcommand.