Expected Behavior
doc provides guidance on how to install pds and it's requirements in a way that won't endanger filling up the disk
Actual Behavior
default docker installation ('yum install docker') places the demon logs to /var, and default pds installation expects containers to run under long-term conditions, with default logging levels on, and without log-rolling, that eventually results in filling up the disk.
Information
We discovered this on yukon when sys admin Ben Aycock alerted us of error messages
From Ben:
Subject: Anacron job 'cron.daily' on yukon
/etc/cron.daily/mlocate:
/usr/bin/updatedb: I/O error while writing to
`/var/lib/mlocate/mlocate.db.AmSh0G': No space left on device
Which repo (e.g., tx-logging)? pds-release
Expected Behavior doc provides guidance on how to install pds and it's requirements in a way that won't endanger filling up the disk
Actual Behavior default docker installation ('yum install docker') places the demon logs to /var, and default pds installation expects containers to run under long-term conditions, with default logging levels on, and without log-rolling, that eventually results in filling up the disk.
Information We discovered this on yukon when sys admin Ben Aycock alerted us of error messages
From Ben:
Hao found this: https://stackoverflow.com/questions/32070113/how-do-i-change-the-default-docker-container-location
Steps to reproduce the behavior Install docker using defaults, install pds-release, use cli-pds-cp to analyze a few datasets for a couple days.