Self-host Heimdall with Levelrail

Verified

An application dashboard that gathers links to all your self-hosted services on one start page.

  • AuthorlinuxserverVerified by Levelrail
  • LicenceMIT
  • Memory128 MiB
  • Archarm64
  • Services1

How to self-host Heimdall

  1. Pull the images

    One image is pulled on your server.

    Show images
    • lscr.io/linuxserver/heimdall:2.6.3
  2. Create the app

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

  3. Fill in the secrets

    3 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.

Heimdall requirements

Memory
About 128 MiB
Architectures
amd64 image published, arm64 tested
Ports
80
Domain
Optional, an sslip.io address is used without one
Settings
none to fill in
License
MIT, permissive license
  • Verified. Verified on arm64 with image tag 2.6.3. Our CI ran this exact image version and it answered on its health path. Evidence
  • Host ports. It publishes port 80 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 Heimdall. 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 Heimdall docs page.

Deploy Heimdall your way

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

Deploy Heimdall from the CLI

levelrail-cli templates deploy heimdall --name my-heimdall

Deploy Heimdall with the API

Create a token in the dashboard first. This one-click route deploys it as a trial app you can keep or remove.

curl -X POST -H "Authorization: Bearer $TOKEN" \
  https://levelrail.example.com/api/v1/service-templates/heimdall/deploy

Heimdall configuration

Heimdall services

ServiceImagePortsVolumes
heimdall lscr.io/linuxserver/heimdall:2.6.3 80 heimdall_config -> /config

Heimdall environment variables

VariableServiceValue
PGID heimdall Preset by the template
PUID heimdall Preset by the template
TZ heimdall Preset by the template

Ports and volumes

Ports
80
Volumes
1 named mount: heimdall_config -> /config

Heimdall FAQ

How much memory does Heimdall need?

The catalog lists about 128 MiB of memory for Heimdall.

Does Heimdall run on arm64?

For Heimdall, arm64 is tested; amd64 is image published.

What licence is Heimdall under?

Heimdall is licensed under MIT, which is permissive, with few conditions on reuse.

Does Heimdall need configuration before it starts?

No. The template fills in its own defaults.

Which ports does Heimdall use?

Heimdall listens on port 80 inside the stack.

Where does Heimdall keep its data?

In a named volume: heimdall_config mounted at /config.

Can I deploy Heimdall 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 Heimdall, 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 lscr.io/linuxserver/heimdall:2.6.3 is what you deploy there.

levelrail-cli templates deploy heimdall --name my-heimdall