Hi GitLab Team,
GitLab CI/CD provides a caching mechanism that can be used to save time
when your jobs are running. (Caching in GitLab CI/CD)
Caches define their paths relative to the project directory, and can’t link to files outside it.
Repository are being saved as tgz or zip files in /var/opt/gitlab/gitlab-rails/shared/cache/archive and taking up tens of GB of disk space until manually cleared out.
Is this /var/opt/gitlab/gitlab-rails/shared/cache/archive/ directory containing some images associated with the container regstry, too?
I would just confirm, whether I should surely remove too old project data or there is also some build images can be stored and used by user’s CI/CD pipeline with caching for image? I need to have some more disk space in gitlab-rails node.
This cache file was created and never modifed for last 6 Months. I have taking a look zip file inside, all project’s main branch was stored and seems no container images associated container registry are stored temporally as a caching.
I would just check from experts.
Is there a container image caching in /var/opt/gitlab/gitlab-rails/shared/cache/archive/?
Best regards,
Donghee.