Analytics cookies only (Google Analytics, PostHog). No ad networks, no cross-site tracking. See our privacy policy.
DR
Self-host Docker Registry UI
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 →
A web interface for a Docker registry, not a registry itself: it is a static single-page app served by nginx that talks to the HTTP API of an existing Distribution (Docker Registry) v2 or v3 server. It lists repositories and tags, shows image details such as size, digests and the layer history, and can delete tags when the registry has deletion enabled. It can point at one registry or let you switch between several, and it supports basic authentication. It has no database of its own; with the nginx proxy option the UI and the registry answer on the same address, which avoids CORS configuration.
Pick Docker Registry UI when you already run (or are about to run) the plain Distribution registry and only want a browser view of it: repository and tag lists, image details with digests and sizes, and tag deletion. Be clear about what it is: a static single-page app served by nginx, written with the Riot library and AGPL-3.0 licensed, that calls the registry's HTTP API; it stores nothing, has no accounts and does not replace a registry. The README says it supports both Docker registry v2 and v3. Our snippet pins `joxit/docker-registry-ui:2.6.0` (released 2026-01-19) and `registry:3.1.2`, and uses the README's recommended layout in which the UI's nginx proxies to the registry (`NGINX_PROXY_PASS_URL`), so the UI and the registry share one address and no CORS headers are needed. We did not find an upstream RAM minimum, so our 64 MB floor is an estimate for a static page behind nginx. In the catalog, Distribution is the registry engine with no interface, zot is a single-binary OCI registry that has its own web UI and search, and Harbor is the full team platform with projects, role-based access, replication and scanning (our floor for it is 4096 MB). Choose this UI over zot or Harbor if you want to keep the standard `registry` image and add a viewer, not change registry.
What you need
Any VPS with at least 64 MB of RAM
A domain you control — most self-hosted setups need HTTPS in front of them
Docker Registry UI's README and FAQ flag these before you rely on it:
non-negotiableDeleting in the UI removes only the manifest reference, not the stored blobs. The README says you must run the registry's garbage collector (registry garbage-collect config.yml) to reclaim space, and that the collector does not remove repositories left empty, which stay listed until you delete their folder in the registry data. Deletion is enabled on the API by REGISTRY_STORAGE_DELETE_ENABLED=true on the registry, which our snippet sets; DELETE_IMAGES only shows the delete controls in the UI.
non-negotiableOur snippet runs the registry with no authentication, so anyone who can reach port 8080 can list, pull, push and delete tags (our snippet enables deletion on the registry). The UI supports only basic authentication, taken from the browser; if you put basic auth in front of the registry, set REGISTRY_SECURED=true (an optimisation that halves the calls to the registry, not a requirement), and put TLS in front, because the README's answer to HTTPS is a reverse proxy.
non-negotiableThe registry URL is plain HTTP on a bare port. The README notes a Docker client needs configuring before it will use an insecure registry, so add the address to insecure-registries on every pushing machine, or terminate TLS in front and use a real hostname.
non-negotiableIf you serve the UI from a different host than the registry instead of proxying, the README warns that Distribution answers CORS preflight requests with 401 when authentication is on, and that this will not be fixed upstream (distribution#4458). Its recommended fixes are the same-address layout we use, NGINX_PROXY_PASS_URL, or a proxy in front of the registry that returns 200 to OPTIONS.
non-negotiableThe UI shows the compressed layer size, which differs from the extracted size that docker images prints.
Docker Registry UI used 14 MB of RAM at idle on GCP e2-standard-2 · Ubuntu 26.04 LTS · Docker 29.9.3 (first boot, measured Nov 2026). We list a minimum of 64 MB.
Is the Docker Registry UI install snippet verified?
The Docker Registry UI install snippet is marked verified on Ubuntu 26.04 (Nov 2026).