hi all,

 

i have 6.4.1 and activated log rotation for the first time, after discovering that this command works like a charm (from another thread): 

logs=$(find /var/lib/docker/containers/ -name '*.log');for log in $logs; do cat /dev/null > $log;done

and in that thread I learned about log rotation but its not working and so my docker.img is running full. only the above command helps to drop it from 8.9GB/10GB to 1.32GB

can you help figure out whats wrong?

Edited February 15, 20188 yr by phenomeus

3 minutes ago, phenomeus said:

hi all,

 

i have 6.4.1 and activated log rotation for the first time, after discovering that this command works like a charm (from another thread): 

logs=$(find /var/lib/docker/containers/ -name '*.log');for log in $logs; do cat /dev/null > $log;done

and in that thread I learned about log rotation but its not working and so my docker.img is running full. only the above command helps to drop it from 8.9GB/10GB to 1.32GB

can you help figure out whats wrong?

 

I've never had an issue with my docker.img filling up.  If I was going to take a guess on how log rotation works, it only takes effect the next time the log for container xxx has to rotate due to size.

 

Your better off right now that you've got your image down to 1.32G to see if it keeps massively growing due to logging by out of control application settings.

its logging like this the ~5th time in a row. and this started with 6.4.1. 

have to check every app if there is something different…