You can now build your own images. This module is about where they live: how to store them, version them, and share them so that other machines, teammates, and servers can run them.
A container registry is a service that stores and distributes container images. Inside a registry, images are organised into repositories, and each version of an image in a repository is identified by a tag. Docker Hub is the default public registry, and the workflow is the same everywhere: docker login to authenticate, docker tag to name the image for a repository, docker push to upload it, and docker pull to download it on another machine.
Public, private, and self-hosted registries each have a place. Cloud providers offer managed options such as Amazon ECR, Azure Container Registry, and GitHub Container Registry, and you can also run your own with the registry image or Harbor. Good tagging, such as version numbers instead of relying on latest, makes deployments repeatable. Watch the lessons in order, then continue on to Running Containers & Networking.
What a registry is and how it acts as the storage and distribution system for Docker images.
The basics of Docker Hub, including how to push your own images to it and pull images back down.
How to name and version your Docker images with tags so you can tell releases apart and deploy them predictably.
A look at a managed cloud registry: AWS's fully managed service for securely storing, sharing, and deploying container images.
How container registries work and how to run one yourself instead of relying on an outside provider.