oci-registry is an implementation of the OCI Registry spec with filesystem and S3 storage back-ends.
https://github.com/mcronce/oci-registry
Features
- Pull-through cache for _any_ registry, not just docker.io
- This includes private, authenticated registries. **This means that you can create an unauthenticated mirror of a private registry and expose it to the Internet. Easily. Don't do that.**
- Two storage back-ends
- S3
- Local filesystem
- Small footprint; in my test system, the official `registry` uses approximately 130 MiB of memory to mirror docker.io; five replicas of `oci-registry` combined use approximately 60 MiB to mirror everything in [example.yaml](example.yaml), plus one private registry. CPU is negligible for both.
- Developed at Virtualization:containers
- Sources inherited from project openSUSE:Factory
-
1
derived packages
- Download package
-
Checkout Package
osc -A https://api.opensuse.org checkout openSUSE:Factory:Rebuild/oci-registry && cd $_ - Create Badge
Refresh
Refresh
Source Files
| Filename | Size | Changed |
|---|---|---|
| _service | 0000000811 811 Bytes | |
| _servicedata | 0000000237 237 Bytes | |
| oci-registry-0.4.5.obscpio | 0000194571 190 KB | |
| oci-registry.changes | 0000000234 234 Bytes | |
| oci-registry.obsinfo | 0000000101 101 Bytes | |
| oci-registry.spec | 0000003562 3.48 KB | |
| vendor.tar.zst | 0037501402 35.8 MB |
Latest Revision
Ana Guerrero (anag+factory)
accepted
request 1207156
from
Johannes Kastl (ojkastl_buildservice)
(revision 1)
new package oci-registry: OCI Registry with filesystem and S3 storage back-ends
Comments 0