download leftovers in /tmp consume disc space

[niziak]

Hello.
We are using lava-gitlab-runner in Docker container. After some time of usage I noticed that free disc space was exhausted due to lots of old artifacts in /tmp folder:

1.5G	./.tmphgGVfA/1295647/artifacts
1.5G	./.tmphgGVfA/1295646/artifacts
1.5G	./.tmphgGVfA/1295648/artifacts
4.3G	./.tmphgGVfA
2.5G	./.tmpMBeEzt/1323217/artifacts
1.5G	./.tmpMBeEzt/1323236/artifacts
2.5G	./.tmpMBeEzt/1323238/artifacts
2.8G	./.tmpMBeEzt/1323215/artifacts
9.2G	./.tmpMBeEzt
14G	.
14G	total

I assume that files are using for cache according to used method.download and it is OK to have temporary cache.
Current status is:

• tmp usage is not limited
• if container is restarted, new random /tmp/tmp... subfolder is created and old artifacts still occupy space.

It would be nice to have option to setup cache directory and its maximum size.

[sjoerdsimons]

That's surprising as these all should be cleaned out after the jobs are done. Is that not happening for you for some reason?

For things left over when you stop the container (due to jobs still running when the container is stopped). That's something that could be improved, but that's something we'd normally assume the container management does already (by virtue of tmp being on tmpfs or another non-persistent location after the container stops)