The first line (the line that matched the start pattern) does not need to match the ContinueThrough pattern.

This is useful in cases where a log message ends with a continuation marker, such as a backslash, indicating that the following line is part of the same message.Īll consecutive lines matching this pattern are included in the group. Or if you want to stop daemon logging altogether the in the daemon.All consecutive lines matching this pattern, plus one additional line, are included in the group. You can modify the days or size values according to your infra availability to keep it as clean as possible. This would keep a maximum of 5 files with a max size of 100mbĬ) then run cat /dev/null > /var/lib/docker/containers/CONTAINER_ID/CONTAINER_ID-json.log #this is to clear out the existing logfileĭ) Finally re-run the script i.e./ launch-harness-delegate.sh Sudo docker run -d -restart unless-stopped -log-driver json-file -log-opt max-size=100m -log-opt max-file=5 -hostname=$(hostname -f) –log-driver json-file -log-opt max-size=100m -log-opt max-file=5 the docker run should look something like: launch-harness-delegate.sh by adding following lines to it: sudo docker stop & sudo docker rmī) inside the harness-delegate-docker/ folder modify our launch script i.e. If you’re using are using the docker image delegate what they need to do is:Ī) stop the docker container i.e. This will rotate the files daily and keep a max of 3 files in the directory /var/lib/docker/containers/*Īnd run cat /dev/null > /var/lib/docker/containers/CONTAINER_ID/CONTAINER_ID-json.log #this is to clear out the existing logfile The logs which are filling up are /var/lib/docker/containers//-json.log therefore:Ĭreate a new logrotate file /etc/logrotate.d/docker-container and a conf file at /etc/nf add same line to both as below: /var/lib/docker/containers/*/*.log

On CentOS, RHEL and Fedora - yum update & yum install logrotate

On Debian and Ubuntu - sudo apt-get update & apt-get install logrotate -y If a container is high usage like delegate or is up for a long time, setting up a log rotate mechanism is very important to avoid disk crashing. If you are running containers on a linux environment, by default the docker engine produces daemon logs stored in different location based on the linux flavour.

Docker daemon logs setting