-
|
I'm researching the possibility of mirroring ostree-compatible OCI distro images. I particularly am interested in mirroring universal-blue images as I'm a user of those distros. Those OS images are signed via cosign and pushed to github container registry. I'm thinking for setups like a private organization, or even LAN parties (eg. getting people to install Bazzite quickly), you don't want each and every workstation/laptop/device/etc. to each go out separately to the WAN to fetch images and saturate the WAN link when an update comes, you'd rather want to manage updates via a central mirror on the LAN. With regular Fedora you can do this via MirrorManager by setting up a local LAN mirror and have clients auto-discover the LAN mirror. How would you set up a similar seamless automatic mirror discovery mechanism that works with rpm-ostree? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
I think https://github.com/containers/image/blob/2ba51d7e51ff487f40370b529fdac5d6a198dc5f/docs/containers-registries.conf.5.md?plain=1#L70 is probably the closest thing here (so requires client configuration). This applies to all of containers/image, so e.g. it'll also be respected by |
Beta Was this translation helpful? Give feedback.
I think https://github.com/containers/image/blob/2ba51d7e51ff487f40370b529fdac5d6a198dc5f/docs/containers-registries.conf.5.md?plain=1#L70 is probably the closest thing here (so requires client configuration). This applies to all of containers/image, so e.g. it'll also be respected by
podman/skopeo(which is what rpm-ostree/bootc uses underneath). I don't think there's anything built-in that'll do mDNS-like auto-discovery.