Rebase `registry/v2` image onto Alpine
Feature description
Was wondering what the appetite for an Alpine version of the opensource/docker/registry-v2
image would be given that that is an option for Iron Bank images now.
Use cases
Currently the Iron Bank version of the registry-v2
image is ~10x larger than its upstream counterpart (https://registry.hub.docker.com/_/registry/tags) which increases the size of installs and can also introduce differences in behavior between the distro baselines (RHEL UBI / Alpine) (https://github.com/docker/distribution-library-image/blob/master/Dockerfile)
Benefits
Switching to Alpine would allow the images to more closely match one another and would allow for more flexible uses of the image (for example, Zarf, an open source project I maintain uses this image as a lightweight way to have a registry running in an airgapped environment - at its size in Iron Bank though registry-v2
is no longer a great lightweight option for smaller utility k8s clusters).
Requirements
The choosing a base image guide would need to be followed to properly update the image: https://docs-ironbank.dso.mil/hardening/choosing-base-image/
Links / references
https://github.com/docker/distribution-library-image https://docs.zarf.dev/docs/contribute-to-zarf/nerd-notes#zarf-architecture
Tasks
-
Feature has been implemented
Please read the Iron Bank Documentation for more info