Skip to content
This repository has been archived by the owner on Dec 24, 2019. It is now read-only.

Workaround for the storage limit on oss-app #108

Open
MarcioMateus opened this issue Sep 30, 2019 · 4 comments
Open

Workaround for the storage limit on oss-app #108

MarcioMateus opened this issue Sep 30, 2019 · 4 comments

Comments

@MarcioMateus
Copy link
Contributor

MarcioMateus commented Sep 30, 2019

The Docker storage limit imposed by the Overlay2 storage driver seems to be the cause of several issues: #107, crossminer/scava#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 the container:/ossmeter/git folder. But will be populated as deltas are created.

@mhow2
Copy link
Contributor

mhow2 commented Sep 30, 2019

I would opt for the second solution.
Can you inform what's the current overlay2 limit ?

@MarcioMateus
Copy link
Contributor Author

I would opt for the second solution.
Can you inform what's the current overlay2 limit ?

It seems to be 10 GB

@MarcioMateus
Copy link
Contributor Author

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.

@MarcioMateus
Copy link
Contributor Author

10f52ac implements the second approach

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants