Making statements based on opinion; back them up with references or personal experience.

The external log deletion could happen while docker is writing json formatted data to the file, resulting in a partial line, and breaking the ability to read any logs from the docker logs cli.

This is done with additional flags to dockerd if you are using the default JSON logging driver.

Make sure to run a systemctl reload docker after changing this file to have the settings applied.

Note, existing containers need to be deleted and recreated to receive the new log limits.

It takes the same max-size and max-file options, but instead of storing in json it uses a binary syntax that is faster and smaller.

This allows you to store more logs in the same sized file.

The daemon.json entry for that looks like.

So if you use a tool like filebeat to send to Elastic, or Splunks universal forwarder, Id avoid the local driver.

Also had to brand create new containers before it took effect.

For instance, after docker-compose restart, I would love to have the mechanism to do something with the preserved logs.

If you can do the latter, then recreating the container with the logging options would be my advice.

The new container has no old logs, and new logs will be rolled automatically, solving both the short term and long term issue at the same time.

If you are unsure, you can just check with ls varlibdockercontainers-json.log what is being truncated.

Using the docker facility is probably much wiser.

BMitch).

The command we run is the familiar truncate -s0 LOGPATH from non-Mac answers.

You can find scripts examples here (read from the bottom): Feature: Ability to clear log history 1083.

And yes, youre right: docker run commands and docker-compose parameters do only affect newly created containers - as opposed to the answer here with the most votes which affects only restarted dockerd daemons and is available through root access only.

My answer is supposed to show a much simpler and updated path than editing than restarting the entire dockerd process.

Docker is installed through Snap, so the path to containers is more like.

You can instead run docker run -ti -v varlibdockercontainers:varinception centos bash then truncate --size 0 varinception08d29a7d469232cfef4456dc6eebcbf313bf01ba73e479520a036150c5ab84de08d29a7d469232cfef4456dc6eebcbf313bf01ba73e479520a036150c5ab84de-json.log.

But there are various situations where the other answers cannot help (if using a remote docker server or working on a Windows machine).

Provide details and share your research But avoid Asking for help, clarification, or responding to other answers.

Docker For Mac Factory Reset