I think there were talks on integrating logrotate for docker containers.
Since logging to a file of 10GB+ of size add high cpu usage and such.
But I see now in docker logs for a container:
# docker logs inc_mainnet reading config file /tmp/logrotate error: /tmp/logrotate:3 unknown option 'secondly' -- ignoring line error: /tmp/logrotate:8 unknown unit 'm' error: found error in /data/*.txt , skipping removing last 1 log configs Reading state from file: /var/lib/logrotate.status Allocating hash table for state file, size 64 entries Handling 0 logs
probably someone tries incorporating logrotate which is good
but probably something is miss configured no?