I built summ as a fully self-contained and feature rich container registry. You can host it on your own server, and push/pull Docker images and Helm charts.
What's there:
- One binary with no external database or sidecar, and a web UI embedded in it
- Passes the OCI conformance suite (862 checks, 0 failures at 1.1), including the referrers API
- Can host very large number of repositories; the target is 10M repos
- Tag history, pull counts, and API-key auth (open / public-pull / private)
Several use cases I can think of:
- Use it as an ephemeral registry for CI
- Caching frequently used open source images internally (e.g. for your Kubernetes cluster)
- Visualizing image pull stats without building an analytics layer
I'd especially like to hear from people running large registries: what breaks for you today?
2 comments
[ 0.21 ms ] story [ 5.3 ms ] threadWhat's there: - One binary with no external database or sidecar, and a web UI embedded in it - Passes the OCI conformance suite (862 checks, 0 failures at 1.1), including the referrers API - Can host very large number of repositories; the target is 10M repos - Tag history, pull counts, and API-key auth (open / public-pull / private)
Several use cases I can think of: - Use it as an ephemeral registry for CI - Caching frequently used open source images internally (e.g. for your Kubernetes cluster) - Visualizing image pull stats without building an analytics layer
I'd especially like to hear from people running large registries: what breaks for you today?