4 ms·
Where I work we've (relatively) recently migrated to using GitLab EE which comes with its own container registry[1]. I have no idea how much work it is behind t
by tempay 9y ago
Where I work we've (relatively) recently migrated to using GitLab EE which comes with its own container registry[1]. I have no idea how much work it is behind the scenes from my perspective it has been flawless and much more convenient.
[1] https://docs.gitlab.com/ce/user/project/container_registry.html https://docs.gitlab.com/ce/user/project/container_registry.h...
- Drdrdrq 9y agoIt is available in Gitlab CE too - we don't use it yet as we already have one in-house, but we might migrate in future.
- nadavami 9y agoWe've been using it where I work for a few months and have recently moved to Artifactory. Mainly because GitLab's registry makes it very very painful to remove old images, (you have to remove them from the UI one by one), especially when the number of registries and images grows.
- grzesiekb 9y agoWe know that this is a real problem for many users. We plan to resolve it as soon as possible. For now you can use our custom tool that removes old revisions, see https://gitlab.com/gitlab-org/docker-distribution-pruner https://gitlab.com/gitlab-org/docker-distribution-pruner. We also have a few issues about this, see https://gitlab.com/gitlab-org/gitlab-ce/issues/25322 https://gitlab.com/gitlab-org/gitlab-ce/issues/25322 and https://gitlab.com/gitlab-org/gitlab-ce/issues/20247 https://gitlab.com/gitlab-org/gitlab-ce/issues/20247. I hope it helps!