3 ms·
Most organizations are not Google or Facebook or Uber, so setting up a P2P network of registries is ghoulish overkill. Any image registry with a HA setup (e.g.
by majewsky 6y ago
Most organizations are not Google or Facebook or Uber, so setting up a P2P network of registries is ghoulish overkill. Any image registry with a HA setup (e.g. API pods in Kubernetes and backing storage in Ceph or a NetApp cluster or whatever) is probably enough.
Source: I've implemented a federating image registry for use at $dayjob (https://github.com/sapcc/keppel https://github.com/sapcc/keppel). Before doing so, I evaluated the landscape and also looked at Kraken briefly.
- jacques_chester 6y agoThanks for the keppel link. Impressive work.
- LockAndLol 6y agoSince you have experience writing your own registry, do you think it would be difficult to support IPFS (or a similar distributed storage technology) for pulling images? I'm thinking HTTP for metadata and IPFS for storage could reduce the load on registries significantly, but I know very little about registries.
- majewsky 6y agoConceptually, no big deal. Most registries already deliver blob contents from a CDN or object store (via HTTP redirect). However, the registry protocol (i.e. the Open Containers Distribution API) only knows HTTP, so you'd have to use a HTTP-to-IPFS proxy to use the IPFS backing store with existing clients.