We have around 158 GiB in /var/opt/gitlab/gitlab-rails/shared/registry/docker/registry/v2/blobs, that seems like rather much (especially if I’m right in how useless most of that is)
As far as I have found out, that is docker images from old builds, if that’s true, they’re not needed. (New builds can be made)
We have quite a few projects (currently around 2900), and I have no involvement in most of them, so I would really really prefer not having to visit each of them in them web interface to do anything, but I don’t mind using being the big bad admin that breaks the possibility to do something to old builds.
No, it doesn’t help. Once again it’s a feature aimed at developers, not those of us who have to administrate a GitLab server.
There are two problems with it:
It’s per project - i.e. it’s painful to use when I want to clean all projects.
It doesn’t directly help me freeing disk space, because it only removes tags so the garbage collection will free some space. (at least that’s how the other delete command works, I haven’t actually tried the bulk deletion, it doesn’t give much when you already have to loop over projects)
Once again (I’ve found many) a sign that GitLab favours usability for developers over maintainability for those of us who has to keep it running.
I didn’t resolve it in the sense that I found a useable feature in GitLab. But I did get to a state we can live with by writing a 119 line (so not completely trivial) Perl-script to run from a systemd timer. It was written on company time, so it’s probably owned by the company I work for, so I can’t just give out copies.
)
