The apimeister-registry engine
Everlock's container registry is powered by [**apimeister-registry**](https://codeberg.org/apimeister/apimeister-registry) — a standalone, open-source OCI Distribution runtime. Everlock embeds that en
Documentation
Tag: registry
Private networks: mDNS discovery
On a home or office LAN there is often no DNS server you control. The OCI backend is still host-routed, so clients need a hostname that resolves to the box. Everlock solves this with **mDNS**: any reg
Public hosting: DNS vhosts and ACME
This page covers reaching an OCI registry from the public internet: how a DNS hostname routes to a registry instance, and how Everlock issues and renews its TLS certificate automatically. It builds on
Registry model and auth reference
This page covers registry storage, routing, and access control for Everlock's OCI service. The Distribution protocol itself comes from the embedded [apimeister-registry](/docs/oci/apimeister-registry)
Getting started: OCI registry
This guide walks through a local first run of Everlock's OCI backend: - start Everlock with one OCI registry bound to `localhost` - create a user through the admin SSH console - log in with Podman - p
OCI backend
The OCI backend turns Everlock into a self-hosted container registry. It serves the OCI Distribution API over HTTP, stores registry data inside Everlock-managed storage, and authenticates access throu