Deploying a private Docker registry with S3 storage
The Docker registry is a central image distribution service. When we pull or push an image, it's from the Docker registry. It can be commercially hosted (CoreOS Quay https://quay.io/ is an example, Docker's own https://hub.docker.com/ is another), or it can be self-hosted (for privacy, speed, bandwidth issues, or company policy). Docker Inc. made it simple for us to deploy it; it's extensively documented and packaged. Amongst the many deployable features, we'll start by simply deploying a single registry ready to be load-balanced, and then we'll switch its backend storage to AWS S3, so disk space will never be an issue again.
Getting ready
To step through this recipe, you will need the following:
- A working Docker installation
- An AWS account with full S3 access
How to do it…
We'll use Docker Compose to work through this recipe. Our objective is to host our own private Docker registry, initially using local...
