Self-host Diun with Levelrail

Watches your running containers and notifies you the moment a new image tag is published.

  • Authorcrazy-max
  • LicenceMIT
  • Memory128 MiB
  • Archarm64
  • Services1

How to self-host Diun

  1. Pull the images

    One image is pulled on your server.

    Show images
    • crazymax/diun:4.29.0
  2. Create the app

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

  3. Fill in the secrets

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

Diun requirements

Memory
About 128 MiB
Architectures
amd64 image published, arm64 image published
Ports
none
Domain
Optional, an sslip.io address is used without one
Settings
none to fill in
License
MIT, 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 Diun. 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 Diun docs page.

Deploy Diun your way

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

Deploy Diun from the CLI

levelrail-cli templates deploy diun --name my-diun

Deploy Diun 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/diun/deploy

Diun configuration

Diun services

ServiceImagePortsVolumes
diun crazymax/diun:4.29.0 none diun_data -> /data

Diun environment variables

VariableServiceValue
DIUN_PROVIDERS_DOCKER diun Preset by the template
DIUN_PROVIDERS_DOCKER_WATCHBYDEFAULT diun Preset by the template
DIUN_WATCH_SCHEDULE diun Preset by the template
DIUN_WATCH_WORKERS diun Preset by the template
LOG_LEVEL diun Preset by the template
TZ diun Preset by the template

Ports and volumes

Ports
none
Volumes
1 named mount: diun_data -> /data

Diun FAQ

How much memory does Diun need?

The catalog lists about 128 MiB of memory for Diun.

Does Diun run on arm64?

For Diun, an arm64 image is published; amd64 is image published.

What licence is Diun under?

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

Does Diun need configuration before it starts?

No. The template fills in its own defaults.

Where does Diun keep its data?

In a named volume: diun_data mounted at /data.

Can I deploy Diun 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 Diun, 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 crazymax/diun:4.29.0 is what you deploy there.

levelrail-cli templates deploy diun --name my-diun