Hi,
I would like to know why the log files and Docker images are really big in my Open edX installation, I am using JUNIPER and the latest version of Tutor.
all.log >> +15GB
tracking.log >> 800MB
Also, a couple of Docker images are really big 12GB and 90GB.
May I know If I need to configure something in Tutor to reduce the increase of these files?
Or I need to make a maitenance in the files and image, if so, what´s commands can I use
These log files are large because, well, you’ve had a lot of traffic for a long time The LMS and CMS store all logs to all.log, and tracking logs, which are then used for analytics, are stored in tracking.log. If you have no use for these files you can simply delete them.
I find this surprising. Are you talking about Docker images or containers? Which ones? How did you discover that? The largest Docker image in Tutor is “openedx” which should not exceed ~824 MB (Docker).
Btw @herwingrodriguez if you are running Juniper then it means that you are definitely not running the latest version of Tutor. After Juniper, Tutor was upgraded to Koa (December 2020) and Lilac (June 2021).
I believe running docker system prune -f should be safe, since you will not prune volumes. But it’s not going to resolve you main issue, which is that you have a single container using up a lot of space.
I cannot help you further because you did not indicate what command you used to print the space used by the containers. Is it the space used by the Docker log files? Is it the container itself? If the container generates a lot of data inside of itself, then we have a problem. We are not supposed to accumulate a lot of data like this. If it’s simply the Docker process which is collecting container logs in the file system, then the problem will go away by restarting the lms container.
Can you please find out which file(s) are taking up the most space in /var/lib/docker/containers/c32d1dc6d8e18e2559b699df339ca91da6d1500f2f8aa42953a59da560411744?
This is the log file generated by Docker that includes all the logs emitted by the container since it started. Just restart the container (tutor local restart lms) and it should go away.