Index | index by Group | index by Distribution | index by Vendor | index by creation date | index by Name | Mirrors | Help | Search |
Name: oci-registry | Distribution: openSUSE Tumbleweed |
Version: 0.4.5 | Vendor: openSUSE |
Release: 1.1 | Build date: Wed Oct 9 15:13:44 2024 |
Group: Unspecified | Build host: reproducible |
Size: 11085401 | Source RPM: oci-registry-0.4.5-1.1.src.rpm |
Packager: https://bugs.opensuse.org | |
Url: https://github.com/mcronce/oci-registry | |
Summary: OCI Registry with filesystem and S3 storage back-ends |
oci-registry is an implementation of the OCI Registry spec with filesystem and S3 storage back-ends. 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, plus one private registry. CPU is negligible for both. Limitations - Pushing is not currently implemented; oci-registry only supports being a pull-through cache (a mirror) at this time. Push support is planned. - Authentication is not currently implemented, but is planned - Only SHA256 content hashes are supported, but supporting other schemes is planned - Connecting to oci-registry with TLS (https) is not supported and support will not be added. - Using nginx as a TLS termination proxy is easy, well-supported, and well-documented; if you require TLS between the client and oci-registry, that is the recommended configuration - Connecting to upstream registries with TLS is supported, recommended, and usually required. - If two clients request the same blob simultaneously, it will be downloaded from upstream twice in parallel instead of having the later request wait for the download to finish, then serve it from cache. There are no data corruption issues, but it is suboptimal. No fix is currently planned, but I'm open to one. - Has not yet had the OCI distribution spec conformance test suite run against it; only manual compatibility testing with docker and containerd has been performed. This is planned after push support is implemented.
MIT
* Wed Oct 09 2024 Johannes Kastl <opensuse_buildservice@ojkastl.de> - new package oci-registry: OCI Registry with filesystem and S3 storage back-ends
/usr/bin/oci-registry /usr/share/doc/packages/oci-registry /usr/share/doc/packages/oci-registry/README.md /usr/share/licenses/oci-registry /usr/share/licenses/oci-registry/LICENSE
Generated by rpm2html 1.8.1
Fabrice Bellet, Sat Dec 7 23:33:42 2024