🚀
booster
Makes synchronization of container images between registries faster.
Requirements
- Two or more container registries to synchronize
- Access to their backing storage directory (for now)
Demo
Set up a demo environment with two local Registry containers, each with its booster:
# Start a "primary" registry backed by a local directory
docker run -d \
-p 5001:5000 \
-v `pwd`/primary:/var/lib/registry \
registry:2
# Start a companion booster container for the primary
PRIMARY_BOOSTER_ID=$( \
docker run -d \
-p 5002:5000 \
-v `pwd`/primary:/var/lib/registry \
ghcr.io/moio/booster:latest \
)
# Start a "replica" registry backed by another local directory
docker run -d \
-p 5003:5000 \
-v `pwd`/replica:/var/lib/registry \
registry:2
# Start a companion booster container for the replica
# Link it to the primary booster
docker run -d \
-p 5004:5000 \
-v `pwd`/replica:/var/lib/registry \
--link $PRIMARY_BOOSTER_ID:primary-booster \
ghcr.io/moio/booster:latest --primary=http://primary-booster:5000
Load up the primary Registry with an image:
docker pull ubuntu:xenial-20210429
docker image tag ubuntu:xenial-20210429 localhost:5001/ubuntu:xenial-20210429
docker image push localhost:5001/ubuntu:xenial-20210429
Synchronize the replica to the primary's contents via:
curl http://localhost:5004/sync
Then push another image and synchronize again:
docker pull ubuntu:xenial-20210611
docker image tag ubuntu:xenial-20210611 localhost:5001/ubuntu:xenial-20210611
docker image push localhost:5001/ubuntu:xenial-20210611
curl http://localhost:5004/sync
Hacking
Building of release binaries, packages and Docker images is done via goreleaser.
For a snapshot build use:
goreleaser release --skip-publish --snapshot --rm-dist
