Self-host Karma with Levelrail

Alert dashboard that merges and filters alerts from one or more Alertmanager instances into a single view.

  • Authorprymitive
  • LicenceApache-2.0
  • Memory64 MiB
  • Services1

How to self-host Karma

  1. Pull the images

    One image is pulled on your server.

    Show images
    • ghcr.io/prymitive/karma:v0.134@sha256:479c7bfad3c176b9c35c5a48c2ad8fa72d748f204314daff748fb51488f043da
  2. Create the app

    One service starts in a single Compose app, on port 8080.

  3. Fill in the secrets

    1 setting is 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

  • Set the Alertmanager address in the install form to an instance this host can reach, then open the address.

Karma requirements

Memory
About 64 MiB
Architectures
amd64 unknown, arm64 unknown
Ports
8080
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 Karma. 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 Karma docs page.

Deploy Karma your way

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

Deploy Karma from the CLI

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

levelrail-cli templates install karma --name my-karma

Deploy Karma 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/karma/install \
  -d '{
    "name": "my-karma"
  }'

Karma configuration

Karma services

ServiceImagePortsVolumes
karma ghcr.io/prymitive/karma:v0.134@sha256:479c7bfad3c176b9c35c5a48c2ad8fa72d748f204314daff748fb51488f043da 8080 none

Karma environment variables

VariableServiceValue
ALERTMANAGER_URI karma Preset by the template

Ports and volumes

Ports
8080
Volumes
none

Karma FAQ

How much memory does Karma need?

The catalog lists about 64 MiB of memory for Karma.

Does Karma run on arm64?

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

What licence is Karma under?

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

Does Karma need configuration before it starts?

No. The template fills in its own defaults.

Which ports does Karma use?

Karma listens on port 8080 inside the stack.

Can I deploy Karma 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 Karma, 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/prymitive/karma:v0.134@sha256:479c7bfad3c176b9c35c5a48c2ad8fa72d748f204314daff748fb51488f043da is what you deploy there.

levelrail-cli templates install karma --name my-karma