Gitlab hero border pattern left svg Gitlab hero border pattern right svg

Category Vision - Container Registry

Container Registry

The GitLab Container Registry is a secure and private registry for Docker images. Built on open source software, the GitLab Container Registry is completely integrated with GitLab. Easily use your images with GitLab CI, create images specific for tags or branches and much more.

Interested in joining the conversation for this category? Please join us in our public epic where we discuss this topic and can answer any questions you may have. Your contributions are more than welcome.

What's Next & Why

We are actively working on improving the performance and reliability of the garbage collection process to help our customers lower the cost of storage for the Container Registry. gitlab-ce#66347 will iterate on the experimental Docker Distribution Pruner to make it available for usage in production.

We are also working on improving the experience and functionality of deleting images/tags. gitlab-ce#21405 addresses an issue where deleting an image/tag deletes all images/tags with the same image_id. Finally, gitlab-ce#40096 will extend the CI job permisisons model to allow CI_REGISTRY_USER to untag images via GitLab CI.

Maturity Plan

This category is currently at the "Viable" maturity level, and our next maturity target is Complete (see our definitions of maturity levels). Key deliverables to achieve this are:

Competitive Landscape

JFrog and Sonatype both offer support for building and deployin Docker images. GitHub has a product in beta that allows users to authenticate, publish and install packages utilizing Docker.

Container registries such as Docker Hub and Quay offer users a single location to build, analyze and distribute their container images.

GitLab provides an improved experience by being the single location for the entire DevOps Lifecycle, not just a portion of it. We will provide many of the features expected of a Package Management tool, but without the weight and complexity of a single-point solution. We will prioritize security, performance and integration without sacrificing user experience.

Top Customer Success/Sales Issue(s)

The top Customer Success / Sales issue is to improve the visibility and management layer of the Container Registry. The goal of gitlab-ce#29639 is to improve the tracking and display of data to provide a more seamless user experience within GitLab. By completing this issue we will:

Top Customer Issue(s)

The top customer issue is gitlab-ce#21405, which addresses issues with removing tags. Currently, the deletion of a single tag, will delete all tags associated with that image. Resolving this issue will establish an improved tag pruning and deletion process for the GitLab Container Registry.

There are additional top TAM issues identified which are popular amongst our customers:

Top Internal Customer Issue(s)

The top internal customer issue is tied to storage optimization. gitlab-ce#57897 will allow the Infrastructure team to lower the total cost of the Container Registry by implementing in-line garbage collection and removal of blobs.

Top Vision Item(s)

As we see increased adoption and usage of the Container Registry, the need for an improved user interface becomes more important. gitlab-ee#3597 establishes a high-level vision for the future user experience of the Container Registry. In the coming months, we will break this feature into actionable issues and conduct user research to ensure we provide the best experience possible.