Analytics cookies only (Google Analytics, PostHog). No ad networks, no cross-site tracking. See our privacy policy.
Self-host zot
updated Nov 2026deployed by usprices checked · Jul 2026Install verified on Ubuntu 26.04 · Nov 2026 · how we test
We earn commissions when you shop through the links below. Full disclosure →
An OCI-native image registry shipped as a single Go binary: it stores images, Helm charts and other OCI artifacts in the OCI image layout, serves the OCI distribution API, and adds a built-in web UI, image search, optional vulnerability scanning, mirroring from other registries and several authentication options including htpasswd, LDAP, OpenID and API keys. Storage is plain files, or S3 and similar back ends.
Pick zot when you want a small OCI-native registry: one Go binary that stores images and other OCI artifacts in the OCI image layout, serves the distribution API, and adds a web UI, image search, optional CVE scanning, mirroring from other registries and several authentication back ends (htpasswd, LDAP, OpenID, API keys). It is Apache-2.0, and storage is plain files or an S3-style back end. Our snippet runs the `zot-linux-amd64` image from GitHub Container Registry, pinned to a release tag, with the image's default configuration (port 5000, Docker v2 schema 2 compatibility, data in `/var/lib/registry`, the search and UI extensions) plus htpasswd authentication. We did not find an upstream RAM minimum, so our 512 MB floor is an estimate: we measured 122 MB idle on an empty registry, and the CVE scanning our config switches on uses more once images are pushed. The catalog's Distribution is the reference registry with no UI, and Harbor is the large team platform with projects, replication and scanning built in.
What you need
Any VPS with at least 512 MB of RAM
A domain you control — most self-hosted setups need HTTPS in front of them
zot's default configuration and documentation flag these before you push real images:
non-negotiableThe image's built-in configuration has no authentication at all, so anyone who can reach port 5000 can push and pull. We mount our own config.json with an htpasswd file for a single admin user whose bcrypt hash is made with the httpd image's htpasswd; with only authentication configured, every signed-in user can read and write every repository. Use the accessControl section for finer rules.
non-negotiablePort 5000 serves plain HTTP. Docker only talks plain HTTP to localhost; for another host either add the address to the daemon's insecure-registries or, better, put a TLS reverse proxy in front before using it from other machines.
non-negotiableEverything is stored under /var/lib/registry, which our zot_data volume holds, so back it up. The image is a distroless build with only the zot-linux-amd64 binary and no shell or Docker healthcheck; the log level in our config is info, while the image default is debug.
non-negotiableThe registry organisation publishes several images (zot-linux-amd64, the zot-minimal build and others). We use the full one with the UI and search extensions switched on in our config, and pin v2.1.23 (released 2026-11-02); zot-linux-arm64, or the multi-arch ghcr.io/project-zot/zot, covers ARM servers.