---
title: "Deploy Docker Registry UI"
description: "Private Docker registry with Joxit's web UI: browse, push, pull and delete"
category: "Storage"
url: https://railway.com/deploy/docker-registry-ui
---

# Deploy Docker Registry UI

Private Docker registry with Joxit's web UI: browse, push, pull and delete

**[Deploy Docker Registry UI on Railway](https://railway.com/template/docker-registry-ui)**

Machine-readable deploy manifest (JSON, validated by TemplateCI): https://railway.com/deploy/docker-registry-ui/manifest.json

- **Creator:** Agaz Self-Host
- **Category:** Storage

## Template content

### Docker Registry UI https://cdn.jsdelivr.net/gh/aalfath/docker-registry-ui-railway-template@3ec227d545bbad45f4ac11b1a3b17d83d27e593d/icon.png

- **Source:** https://github.com/aalfath/docker-registry-ui-railway-template
- **Health check:** /
- **Public domain:** Yes

### Registry https://cdn.jsdelivr.net/gh/aalfath/docker-registry-ui-railway-template@3ec227d545bbad45f4ac11b1a3b17d83d27e593d/icon.png

- **Source:** https://github.com/aalfath/docker-registry-ui-railway-template
- **Health check:** /

## Documentation

# Deploy and Host Docker Registry UI on Railway

Docker Registry UI by Joxit is an open-source web interface for a private Docker registry (registry v2 API). It lists your repositories and tags, shows image sizes, digests, creation dates and build history, gives you the `docker pull` command, and can delete tags. This template deploys it together with its registry.

## About Hosting Docker Registry UI

Hosting it takes two services: a Docker registry that stores image layers on durable storage behind a login, and the UI that browsers and Docker clients reach over HTTPS. This template builds both from one GitHub repo. The registry (CNCF Distribution 3.1.2) keeps images on a Railway volume, has no public domain, and refuses to start without a password. The UI (2.6.0) gets the public domain and proxies `/v2/` to the registry over the private network, so the web UI, `docker login`, `docker push` and `docker pull` all use the one domain, with no CORS setup. The login password is generated at deploy time.

## Common Use Cases

* Browsing and cleaning up the images your CI pipeline pushes to a private registry
* A private registry with a web view for a team or homelab, without per-seat pricing
* Storing base images and internal tools close to your other Railway services

## Dependencies for Docker Registry UI Hosting

* Docker Registry UI 2.6.0, the official `joxit/docker-registry-ui` image pinned by digest
* CNCF Distribution (`registry`) 3.1.2, the official image pinned by digest, with a Railway volume for images

### Deployment Dependencies

* Docker Registry UI: https://github.com/Joxit/docker-registry-ui
* Release 2.6.0: https://github.com/Joxit/docker-registry-ui/releases/tag/2.6.0
* Distribution 3.1.2: https://github.com/distribution/distribution/releases/tag/v3.1.2
* Registry configuration reference: https://distribution.github.io/distribution/about/configuration/
* Template source: https://github.com/aalfath/docker-registry-ui-railway-template

### Implementation Details

Services:

* **Docker Registry UI** (public): nginx serves the UI and proxies `/v2/` to the registry. Health check `/`.
* **Registry** (private): stores images on its volume at `/var/lib/registry`. Health check `/`.

After the deploy, open the UI's Railway domain. The browser asks for a login: use `REGISTRY_USERNAME` (default `admin`) and the generated `REGISTRY_PASSWORD` from the Registry service's variables. Then push from your machine:

```sh
docker login YOUR-DOMAIN.up.railway.app -u admin
docker tag alpine:3 YOUR-DOMAIN.up.railway.app/tools/alpine:3
docker push YOUR-DOMAIN.up.railway.app/tools/alpine:3
```

Deleting a tag in the UI removes its manifest. To free the space its layers used, set `REGISTRY_GC_ON_START=true` on the Registry service, redeploy it, then remove the variable. Unfinished uploads are purged after 7 days. To change the login, edit `REGISTRY_USERNAME` or `REGISTRY_PASSWORD` and redeploy the Registry service. Optional display settings such as `REGISTRY_TITLE` and `THEME` go on the UI service (see upstream's list of options).

Updates: the services build from the template's GitHub repo, so Railway shows you an "update available" notice when a new version is merged there. You choose when to apply it, and your images stay on the volume. The repo's CHANGELOG.md lists breaking changes first.

## Why Deploy Docker Registry UI on Railway?


Railway is a singular platform to deploy your infrastructure stack. Railway will host your infrastructure so you don't have to deal with configuration, while allowing you to vertically and horizontally scale it.

By deploying Docker Registry UI on Railway, you are one step closer to supporting a complete full-stack application with minimal burden. Host your servers, databases, AI agents, and more on Railway.



## Similar templates

- [RustFS | (Just Updated) S3 Object Store, Public URL and Keys Set](https://railway.com/deploy/rustfs-or-just-updated-s3-object-store-p) — S3-compatible object store, keys and public URL preset, volume kept
- [TimescaleDB](https://railway.com/deploy/timescaledb-railway-template) — A PostgreSQL-based time-series database for analytics on Railway.
- [Neo4j 2026.10 Community](https://railway.com/deploy/neo4j-202610-community) — Neo4j graph database with APOC, Browser, Bolt TCP proxy and a volume

Open this page in a browser: https://railway.com/deploy/docker-registry-ui
