Self-host Kellnr with Levelrail

Self-hosted registry for private Rust crates with a web UI and docs hosting. Runs a single container with data on a volume.

  • Authorkellnr
  • LicenceApache-2.0
  • Memory256 MiB
  • Services1

How to self-host Kellnr

  1. Pull the images

    One image is pulled on your server.

    Show images
    • ghcr.io/kellnr/kellnr:7.1.0
  2. Create the app

    One service starts in a single Compose app, with 1 named volume mount for your data, on port 8000.

  3. Fill in the secrets

    2 settings are preset, you do not have to fill in anything.

  4. Open it

    Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.

After the first start

  • Sign in as admin with the password admin and change it at once, because it is public knowledge. Set the hostname setting to the address you serve it on.

Kellnr requirements

Memory
About 256 MiB
Architectures
amd64 unknown, arm64 unknown
Ports
8000
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 Kellnr. 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 Kellnr docs page.

Deploy Kellnr your way

Every format below deploys the same pinned images. Pick the one that fits how you work.

Deploy Kellnr from the CLI

Add --domain SERVICE=HOST to serve a service on your own domain, for example --domain kellnr=app.example.com.

levelrail-cli templates install kellnr --name my-kellnr

Deploy Kellnr with the API

Create a token in the dashboard first. Name, env and domains are the request fields.

curl -X POST -H "Authorization: Bearer $TOKEN" -H "Content-Type: application/json" \
  https://levelrail.example.com/api/v1/service-templates/kellnr/install \
  -d '{
    "name": "my-kellnr"
  }'

Kellnr configuration

Kellnr services

ServiceImagePortsVolumes
kellnr ghcr.io/kellnr/kellnr:7.1.0 8000 kdata -> /opt/kdata

Kellnr environment variables

VariableServiceValue
KELLNR_ORIGIN__HOSTNAME kellnr Preset by the template
KELLNR_REGISTRY__DATA_DIR kellnr Preset by the template

Ports and volumes

Ports
8000
Volumes
1 named mount: kdata -> /opt/kdata

Kellnr FAQ

How much memory does Kellnr need?

The catalog lists about 256 MiB of memory for Kellnr.

Does Kellnr run on arm64?

For Kellnr, arm64 support is not confirmed; amd64 is unknown.

What licence is Kellnr under?

Kellnr is licensed under Apache-2.0, which is permissive, with few conditions on reuse.

Does Kellnr need configuration before it starts?

No. The template fills in its own defaults.

Which ports does Kellnr use?

Kellnr listens on port 8000 inside the stack.

Where does Kellnr keep its data?

In a named volume: kdata mounted at /opt/kdata.

Can I deploy Kellnr 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 Kellnr, 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/kellnr/kellnr:7.1.0 is what you deploy there.

levelrail-cli templates install kellnr --name my-kellnr