Docker Distribution Pruner from experimental to GA
Problem to solve
As our customers continue to adopt GitLab Container Registry to build and publish images, they are faced with increasing storage costs and a difficult to navigate user interface. This is especially problematic for instances with terabytes of data in their container registry.
In February 2019, we released an experimental version of the docker distribution pruner which was intended to be a more efficient Garbage Collector designed to clean all old revisions from Docker Distribution based registries, including the GitLab Container Registry.
- Self-managed instances that are currently using the container registry and have more than 300 GB of storage currently being used.
- We have a separate issue for improving our existing garbage collection process. We may decide to focus on this issue or that one, depending on the result of our investigations.
Improve the docker distribution pruner and make it generally available to our customers for use in production.