root filesystem disk space and /run/podman/logs/events.log

[Ted_Serreyn]

I noticed that one of my clients with on premise management with root filesystem almost full.  Starting digging into it only to find that this log file in /run/podman/logs/ was quite large.

Is there a reason that this is being written to the /run filesystem and not the /var/log filesystem where all the other logs reside?

Normally the /run filesystem is mounted as a tmpfs from ram, which is cleared every reboot.  Is there a reason that this is set to actually write to disk?

I've been finding a lot of these little overlooked log files on various checkpoint systems that do not seem to be maintained or cleaned up and fill the filesystem over time.

Is there a central SK that keeps track of all these log files?

[Lesley]

I cannot find any information regarding this specific file. That means you have to open TAC case to ask regarding this. But I also know in recent Jumbo's many issues are solved regarding disk space filling up to quickly with different files / backups. What is the version and Jumbo take we are talking about? 

[PhoneBoy]

From a recent TAC case, it seems this will be addressed in a future JHF.
I also found a possible workaround for this in the meantime:

1. Backup and edit "/etc/cpshell/log_rotation.conf" file
2. Add the line: /run/libpod/events/events.log 1048576 10
3. Reboot, after which / usage should decrease