Self-host Docker Registry (Authenticated) with Levelrail
A private container registry with HTTP basic auth baked in at boot, unlike the catalog's open registry entry.
- Memory256 MiB
- Archarm64
- Services1
How to self-host Docker Registry (Authenticated)
-
Pull the images
One image is pulled on your server.
Show images
registry:3
-
Create the app
One service starts in a single Compose app, with 1 named volume mount for your data, on port 5000.
-
Fill in the secrets
2 secrets are generated and stored encrypted, 3 settings are preset, you do not have to fill in anything.
-
Open it
Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.
Docker Registry (Authenticated) requirements
- Memory
- About 256 MiB
- Architectures
- amd64 image published, arm64 image published
- Ports
- 5000
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- not yet recorded
- Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.
- Host ports. It publishes port 5000 on the host, so open them in the VPS firewall only if you want that.
Install Levelrail first
On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then Docker Registry (Authenticated). New to Levelrail? Install it on a fresh VPS first.
docker pull ghcr.io/glincker/levelrail:latest Then levelrail-cli login --device. See Getting started and the Docker Registry (Authenticated) docs page.
Deploy Docker Registry (Authenticated) your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy Docker Registry (Authenticated) from the CLI
levelrail-cli templates deploy docker-registry-auth --name my-docker-registry-auth Deploy Docker Registry (Authenticated) with the API
curl -X POST -H "Authorization: Bearer $TOKEN" \
https://levelrail.example.com/api/v1/service-templates/docker-registry-auth/deploy Docker Registry (Authenticated) configuration
Docker Registry (Authenticated) services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| registry | registry:3 | 5000 | registry_auth_data -> /var/lib/registry |
Docker Registry (Authenticated) environment variables
| Variable | Service | Value |
|---|---|---|
| HTPASSWD_PASS | registry | Generated at deploy |
| HTPASSWD_USER | registry | Generated at deploy |
| REGISTRY_AUTH | registry | Preset by the template |
| REGISTRY_AUTH_HTPASSWD_PATH | registry | Preset by the template |
| REGISTRY_AUTH_HTPASSWD_REALM | registry | Preset by the template |
Ports and volumes
- Ports
- 5000
- Volumes
- 1 named mount: registry_auth_data -> /var/lib/registry
Docker Registry (Authenticated) FAQ
How much memory does Docker Registry (Authenticated) need?
The catalog lists about 256 MiB of memory for Docker Registry (Authenticated).
Does Docker Registry (Authenticated) run on arm64?
For Docker Registry (Authenticated), an arm64 image is published; amd64 is image published.
Does Docker Registry (Authenticated) need configuration before it starts?
No. The template fills in its own defaults and generates secrets at deploy time.
Which ports does Docker Registry (Authenticated) use?
Docker Registry (Authenticated) listens on port 5000 inside the stack.
Where does Docker Registry (Authenticated) keep its data?
In a named volume: registry_auth_data mounted at /var/lib/registry.
Can I deploy Docker Registry (Authenticated) on Dokploy or Dokku?
The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list we compared does not have an entry with the same id for Docker Registry (Authenticated), so on Dokploy you would use a Docker Compose application with the file from this page. Dokku deploys container images with its own commands, so the pinned image registry:3 is what you deploy there.