

Google Container Registry (GCR) provides secure, private Docker image storage on Google Cloud Platform. It provides a single place for teams to manage Docker images, perform vulnerability analysis, and decide who can access what with fine-grained access control. Existing CI/CD integrations let teams set up fully automated Docker pipelines to get fast feedback. Costs for use are based only on Google Cloud Platform storage and network usage.
GitLab also provides a container registry which is a built-in part of the product (ie. no extra costs beyond standard tiered licensing costs for the single GitLab application which provides capabilities for the entire DevOps lifecycle).
FEATURES |
![]() |
|
---|---|---|
Docker image support
Supports storage and retrieval of Docker style containers. |
|
|
Container registry webhooks
Trigger actions after a successful push to a registry to integrate Docker Hub with other services. |
|
|
Container registry high availability
Highly available through the use of multiple replicas of all containers and metadata such that if a machine fails, the registry continues to operate and can be repaired. |
|
|
Container Registry geographic replication
Supports distributed teams by running multiple registry instances across several regions and syncing between data centers. |
|
|
Supports private container registries
Offers the ability to have private container registries and repositories |
|
|
SaaS container registry offering
The container registry ia available as a software service. Learn more about the container registry available on GitLab.com |
|
|
Self-managed container registry offering
Container registry which is available to be self-installed and self-managed in an organizations data center, co-hosted, or in a chosen cloud provider. |
|
|
Use container registry through REST API
Enables support for automation and integration of container registry through a REST API. |
|
|
Lower the cost of storage for the GitLab Container Registry by running garbage collection
In the context of the Docker registry, garbage collection is the process of removing blobs from the filesystem when they are no longer referenced by a manifest. |
|
|
Use search to find and container images
Search your group and project’s Container Registry by image name |
|
|
Helm chart repository support
Supports storage and retrieval of Helm charts. |
|
|
Container image cleanup policies
Easily define, manage and update project-level policies to define which images should be removed and preserved. This feature is designed to help you reduce storage costs and prevent important images from being deleted. |
|
|