Self-host Zot Registry with Levelrail
OCI native container image registry with a web UI, search and optional sync. The install form carries config.json as an editable file and images are stored on a volume.
- Authorproject-zot
- LicenceApache-2.0
- Memory128 MiB
- Services1
How to self-host Zot Registry
-
Pull the images
One image is pulled on your server.
Show images
ghcr.io/project-zot/zot:v2.1.23
-
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
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.
After the first start
- Push an image with docker push to this address, then open the address to browse it. The starter config has no login, so keep it private or add authentication in the config file.
Zot Registry requirements
- Memory
- About 128 MiB
- Architectures
- amd64 unknown, arm64 unknown
- Ports
- 5000
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- Apache-2.0, permissive license
- Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.
Install Levelrail first
On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then Zot Registry. 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 Zot Registry docs page.
Deploy Zot Registry your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy Zot Registry from the CLI
levelrail-cli templates install zot --name my-zot Deploy Zot Registry with the API
curl -X POST -H "Authorization: Bearer $TOKEN" -H "Content-Type: application/json" \
https://levelrail.example.com/api/v1/service-templates/zot/install \
-d '{
"name": "my-zot"
}' Zot Registry configuration
Zot Registry services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| zot | ghcr.io/project-zot/zot:v2.1.23 | 5000 | data -> /var/lib/registry |
Zot Registry environment variables
The catalog lists no environment variables for this template.
Ports and volumes
- Ports
- 5000
- Volumes
- 1 named mount: data -> /var/lib/registry
Zot Registry FAQ
How much memory does Zot Registry need?
The catalog lists about 128 MiB of memory for Zot Registry.
Does Zot Registry run on arm64?
For Zot Registry, arm64 support is not confirmed; amd64 is unknown.
What licence is Zot Registry under?
Zot Registry is licensed under Apache-2.0, which is permissive, with few conditions on reuse.
Does Zot Registry need configuration before it starts?
No. The template fills in its own defaults.
Which ports does Zot Registry use?
Zot Registry listens on port 5000 inside the stack.
Where does Zot Registry keep its data?
In a named volume: data mounted at /var/lib/registry.
Can I deploy Zot Registry 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 Zot Registry, 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 ghcr.io/project-zot/zot:v2.1.23 is what you deploy there.