Open davidediruscio opened 4 years ago
I would opt for the second solution. Can you inform what's the current overlay2 limit ?
I would opt for the second solution. Can you inform what's the current overlay2 limit ?
It seems to be 10 GB
It seems that the container:/ossmeter/git
is not the main culprit for the storage consumption.
container:/root/
is using 6GB on the oss-app
running at http://ci4.castalia.camp. Scava seems to be storing a lot of data there.
https://github.com/crossminer/scava-deployment/commit/10f52ac0ce0b1abec3ae6329cb3a1a171b88afb1 implements the second approach
The Docker storage limit imposed by the
Overlay2
storage driver seems to be the cause of several issues: https://github.com/crossminer/scava-deployment/issues/107, https://github.com/crossminer/scava/issues/390.One possible solution is to change the storage-driver to
devicemanager
and configure a new max limits in the Docker engine. This change would affect all the Docker running on the machine.Another solution is to link the folders that need to store great amounts of data to the host filesystem using volumes. This change can be made on the docker -compose file and any rebuild.
My suggestion is to bind
container:/ossmeter/git
to a folder on the host filesystem. This migration will delete the previous data on thecontainer:/ossmeter/git
folder. But will be populated as deltas are created.