Self-host Uptime Kuma (MariaDB) on a VPS

Uptime Kuma with a MariaDB sidecar provisioned, for the setups that opt out of its default SQLite file.

levelrail-cli templates deploy uptime-kuma-mariadb --name my-uptime-kuma-mariadb

Specification

Status
Listed
Category
Monitoring
Services
mariadb, uptime-kuma
Ports
3001
Volumes
2
Memory
about 512 MiB
arm64
image published
amd64
image published
Settings to fill in
none

About Uptime Kuma (MariaDB)

Uptime Kuma with a MariaDB sidecar provisioned, for the setups that opt out of its default SQLite file. Runs 2 containers (mariadb, uptime-kuma), with uptime-kuma listening on port 3001; data is kept in named volumes.

What it deploys

Uptime Kuma (MariaDB) runs as 2 services in a single Compose app, listening on port 3001, with 2 named volume mounts.

ServiceImageTagPortsVolumes
mariadb mariadb 11 none uptime_kuma_mariadb_data -> /var/lib/mysql
uptime-kuma louislam/uptime-kuma 2 3001 uptime_kuma_mariadb_app_data -> /app/data

Before you install

  • CPU architecture. arm64 listed. Every image lists linux/arm64 in its registry manifest. That is a manifest fact, not proof the app runs on Arm.
  • Listed. It is in the catalog. Back up the data volume before changing an image tag.
  • Host ports. It publishes port 3001 directly on the host, so open them in the VPS firewall only if you want that.

Settings and environment

You do not have to fill in anything. 3 secrets are generated at deploy and stored encrypted. Values are never shown here.

ServiceVariableValue
mariadbMYSQL_DATABASEPreset by the template
mariadbMYSQL_PASSWORDGenerated at deploy
mariadbMYSQL_ROOT_PASSWORDGenerated at deploy
mariadbMYSQL_USERGenerated at deploy
uptime-kumaTZPreset by the template

Install Uptime Kuma (MariaDB) on a VPS

  1. Install Levelrail on a fresh VPS

    Run this as root on a Linux server (amd64 or arm64) with ports 80 and 443 reachable. The installer prints a setup link.

    curl -fsSL https://levelrail.com/install.sh | sudo sh
  2. Sign in

    Open the setup link, choose a password, then log the CLI in. The CLI install command is curl -fsSL https://levelrail.com/install-cli.sh | sh if the machine does not have it. See Getting started.

    levelrail-cli login --device
  3. Read the template

    Shows the entry, including its full compose.yaml.

    levelrail-cli templates get uptime-kuma-mariadb
  4. Deploy it

    This deploys the template compose file as an app. The app name defaults to the template id; --name sets another.

    levelrail-cli templates deploy uptime-kuma-mariadb --name my-uptime-kuma-mariadb

Without a domain the app gets an sslip.io address. You can also deploy it from the dashboard: Apps, New app, Browse templates, then Uptime Kuma (MariaDB).

More in Monitoring

All Monitoring templates