Container Registry
Definition
Google's service for storing and managing Docker container images, enabling easy access and version control for developers and teams.
Use Cases
- Spotify: Store and distribute versioned microservice container images for Kubernetes deployments — Teams build Docker images in CI, tag them with immutable versions (for example, git SHA), push to a private registry, and deploy to Kubernetes clusters using those tags. Access is controlled via cloud IAM and service accounts used by CI and cluster nodes. (More reliable releases through consistent, repeatable deployments and faster rollbacks by redeploying a known-good image tag.)
- The Home Depot: Enterprise container image management for large-scale microservices — Development teams publish container images from CI pipelines to a centralized private registry, apply standardized tagging conventions, and deploy to Kubernetes. Registry access is restricted to approved build systems and runtime identities to reduce supply-chain risk. (Improved deployment consistency across teams and environments, with better governance over what images can be promoted to production.)
Provider Equivalents
- AWS: Amazon Elastic Container Registry (ECR)
- Azure: Azure Container Registry (ACR)
- GCP: Container Registry (GCR) / Artifact Registry (recommended for new use)
- OCI: Oracle Cloud Infrastructure Registry (OCIR)
Frequently Asked Questions
- What's the difference between Container Registry and Artifact Registry?
- Container Registry (GCR) is focused on storing container images. Artifact Registry is Google Cloud’s newer service that can store container images and other artifacts (like language packages) in the same product, with newer features and regional repository options. For most new Google Cloud setups, Artifact Registry is the recommended choice, while Container Registry is often used for existing projects.
- When should I use Container Registry?
- Use a container registry when you need a secure, centralized place to store and version container images that will be deployed to environments like Kubernetes or Cloud Run. On Google Cloud, consider using Artifact Registry for new projects; use Container Registry mainly if you already have existing GCR image paths or legacy workflows that depend on it.
- How much does Container Registry cost?
- Costs typically depend on how much image data you store (storage), how often images are downloaded (network egress, especially across regions or to the internet), and any related operations in your CI/CD pipeline. Pricing varies by region and usage patterns; the biggest cost drivers are usually stored image size, retention of many tags/versions, and cross-region or internet egress when pulling images.
Category: containers
Difficulty: intermediate
See Also