Container Registries
What you'll learn: How container images are stored, versioned, distributed, and shared across teams and infrastructure using container registries.
What Is a Container Registry?
A container registry is a centralized repository for storing and distributing container images. Think of it like a library for books, but instead of books, you're storing container images that can be pulled down whenever you need to run them.
When you build a container image, it lives on your local machine initially. To use that image on other machines, deploy it to production servers, or share it with teammates, you need to push it to a registry. From there, any authorized system can pull the image and run containers based on it.
How Registries Work
Container registries organize images by name and tag. A typical image reference looks like:
registry.example.com/myapp:v1.2.3
registry.example.com— the registry hostmyapp— the image namev1.2.3— the version tag
When you don't specify a registry, most tools default to Docker Hub, the public registry (docker.io).
Public vs Private Registries
Public registries (like Docker Hub) host images anyone can pull — useful for open-source projects and base images like nginx or postgres.
Private registries require authentication and are used for proprietary applications. Popular options include AWS ECR, Google Container Registry, Azure Container Registry, and self-hosted solutions like Harbor.
Versioning and Tagging
Tags let you version your images. Teams often use semantic versions (v1.0.0), environment tags (dev, prod), or Git commit SHAs. The latest tag is common but risky — it's mutable and doesn't guarantee what version you'll actually get.
Key Takeaway: Container registries are centralized storage systems for container images, enabling versioned distribution across environments through a simple push/pull workflow.