EVAL is an educational platform for managing training exercises and exams, featuring specialized question types for software engineering education and training.
Due to the code check sandboxes docker takes increasingly high amount of disk space on the server. Currently over 200Gb.
The idea is to apply the manual procedure to cleanup the disk space that was already done few time, take notes, and build the github workflow that applies that same procedure.
This procedure has no distruptif impact on the running app but can free up most of the disk space usage. A small "degradation" in form of longer time to make the first run of the sandbox on a image that needs to be pulled for the first time is expected after each cleanup.
Sounds like something we shouldn't forget to do periodically. I'm fine with a scheduled workflow. Have you considered setting up a cron on our server for this task?
Due to the code check sandboxes docker takes increasingly high amount of disk space on the server. Currently over 200Gb.
The idea is to apply the manual procedure to cleanup the disk space that was already done few time, take notes, and build the github workflow that applies that same procedure.
This procedure has no distruptif impact on the running app but can free up most of the disk space usage. A small "degradation" in form of longer time to make the first run of the sandbox on a image that needs to be pulled for the first time is expected after each cleanup.