Feature: Ability to clear log history

[djessup]

A feature I've thought would be useful since originally using Fig, and now Compose would be the ability to clear the log history for Composed-managed containers. Long-running or "chatty" containers can end up with a lot of log noise that may not be wanted.

I'd expect a command like the following would solve the problem:
$ docker-compose logs --clear [service]

[dnephin]

I don't think that is a feature supported by the docker daemon. Looking at the api docs, the only option would be to truncate the returned logs to a limited number of lines per container:

https://docs.docker.com/reference/api/docker_remote_api_v1.17/#get-container-logs

[metal3d]

👍 for this issue. I actually use compose to develop a website in Golang, Mongodb and nginx... 5 days after begining I have a long logs that becomes to be worrying. Each time I restart containers append many lines to the log.
@dnephin I don't understand if you give a solution (that I don't understand :)) or if you propose to check if it's possible with api. Sorry for my bad english.

[thaJeztah]

Docker 1.6 will add support for logging drivers, see moby/moby#10568 (currently; JSON, syslog and "none") work is in progress for basic log-rotation; moby/moby#11485

[metal3d]

Good to hear that, thanks a lot :)

[djessup]

Thanks for the background and update on Docker 1.6 - looking forward to it!

[sgarbesi]

docker logs -c (clear) <container> would be great.

+1

[baptistedonaux]

+1 Really important

[egyptianbman]

Holy cow, I just sat through several minutes of logs to get to the end. I'd really appreciate this as well for the sake of not having to rebuild containers constantly.

[jghibiki]

+1

[vronin]

+1

[junajan]

+1

[knutole]

👍

[Rodeoclash]

+1

[nafg]

+2

[FnTm]

+1

[dmage]

Just for the record, with Docker 1.8 and docker-compose 1.4 there is already exists a method to limit log size using https://docs.docker.com/compose/yml/#log-driver and log-opt max-size:

  log_driver: "json-file"
  log_opt:
    max-size: "100k"
    max-file: "20"

[knutole]

@dmage Thanks, exactly what I need.

[OlivierCuyp]

+1000

[sheyman]

+1 would LOVE this

[joegoggins]

+1

[Rodeoclash]

@dmage solution works great for us. Those others who are +1ing this, what is wrong with the solution that he's given?

[rosskevin]

@Rodeoclash - I think one use case for this is reuse of a given set of containers for a new run i.e. CI test run. The old logs are irrelevant to the new run, so a clear prior to the next command would clear up confusion.

[SpeCT]

+1

[ballinette]

+1, same need as @rosskevin

[dnephin]

Ok, to recap:

• you can do this from a compose file (see Feature: Ability to clear log history #1083 (comment))
• limit fig log #265 covers being able to limit the output from the logs command
• "up" displays output from previous runs #1756 covers the re-used container case

Going to close this since it's already support or tracked in other issues.

[ccamacho]

+1

[MPJHorner]

+1

[WhiteBearSpirit]

I made a simple script docker_clear_log.sh:
sudo truncate -s 0 $(docker inspect --format='{{.LogPath}}' $1)
Usage: ./docker_clear_log.sh [Name-or-ID]
Should work if you have sudo rights and log_driver: "json-file" setting for your docker (default).

[gsugambit]

+1

I also tried to temp solution and it appears to work

[educatedwarrior]

The original issue was never resolved and the issue was closed anyway. Interesting. @djessup , how do you like those apples?

[dhakehurst]

would still be nice to have a docker-compose logs --clean

[linvi]

Why has this issue been closed without even a comment when the issue in itself has not been solved?

[Ghoughpteighbteau]

@linvi

When I came to this thread, the closing comment had been folded into other comments. It's right here:

#1083 (comment)

I think they're hoping to cover this particular use case through indirect means. Mention you're particular use case and how it's not covered, and it might help the ticket be re-opened. Worst case, someone might point out an easy way to get what you want :D

[MartinNiederl]

Any updates?

[FelixFurtmayr]

when there is a log, we should be able to clear it in a simple way.

would be really nice, if you could build the command into it. this seems not hard.
thousands of people would be very happy not having to scroll through everything.

[FelixFurtmayr]

If you use docker-compose, use lazydocker for viewing logs. Then there is then no need to delete logs. You get live logs and start with the latest logs. This helps very much with debugging.

https://github.com/jesseduffield/lazydocker
You can install it with one line and it is a good monitoring tool. It is a pitty that people are not so reasonable to understand that a "delete log" function is a good thing.

But the workaround with lazy docker does it for me. Thank you jesseduffield for giving us the possibility to be lazy with your monitoring tool :-)
Maybe consider donating to lazydocker if this makes debugging/monitoring for you also easier.
And for you docker developers / maintainers: why is the interface from docker not like that?
Docker is pretty awesome, but have a look at lazydocker; there is room for improvement.

[GF-Huang]

+2147483647

[kagansari]

+49324893

[bf]

This is such a central problem with UX of docker-compose, I wonder why it has not been resolved. Every time I run docker-compose up, some of the new logs are put on the top of super old logs from 5 starts ago. What is this?

[GF-Huang]

This issue should be re-open.

[ell1e]

I would love to use this as well. Why can't there be a simple docker-compose logs --clean-logs <service>?

[srinitude]

Echoing everyone here lol

[eon01]

A simple workaround for me is using docker-compose up --force-recreate

[srinitude]

@eon01 Awesome hack! Thanks for sharing

[GF-Huang]

7 years passed.

[reesericci]

Please add this!!!

[rentianxiang]

Please add this! And reopen this issue!

[julianoamg]

sudo sh -c "truncate -s 0 /var/lib/docker/containers/**/*-json.log"

[ajs6f]

+1

[PavelNiedoba]

It would make even more sense if you can

docker compose logs clear [all | since | keep lines xxx | you name it]

so it cleans logs for whole stack

also archiving in production environments would be nice