Self-host Uptime Kuma (MariaDB) with Levelrail
Uptime Kuma with a MariaDB sidecar provisioned, for the setups that opt out of its default SQLite file.
- Authorlouislam
- LicenceMIT
- Memory512 MiB
- Archarm64
- Services2
How to self-host Uptime Kuma (MariaDB)
-
Pull the images
2 images are pulled on your server.
Show images
mariadb:11louislam/uptime-kuma:2
-
Create the app
2 services start in a single Compose app, with 2 named volume mounts for your data, on port 3001.
-
Fill in the secrets
3 secrets are generated and stored encrypted, 2 settings are preset, you do not have to fill in anything.
-
Open it
Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.
Uptime Kuma (MariaDB) requirements
- Memory
- About 512 MiB
- Architectures
- amd64 image published, arm64 image published
- Ports
- 3001
- 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.
- Host ports. It publishes port 3001 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 Uptime Kuma (MariaDB). 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 Uptime Kuma (MariaDB) docs page.
Deploy Uptime Kuma (MariaDB) your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy Uptime Kuma (MariaDB) from the CLI
levelrail-cli templates deploy uptime-kuma-mariadb --name my-uptime-kuma-mariadb Deploy Uptime Kuma (MariaDB) with the API
curl -X POST -H "Authorization: Bearer $TOKEN" \
https://levelrail.example.com/api/v1/service-templates/uptime-kuma-mariadb/deploy Uptime Kuma (MariaDB) configuration
Uptime Kuma (MariaDB) services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| 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 |
Uptime Kuma (MariaDB) environment variables
| Variable | Service | Value |
|---|---|---|
| MYSQL_DATABASE | mariadb | Preset by the template |
| MYSQL_PASSWORD | mariadb | Generated at deploy |
| MYSQL_ROOT_PASSWORD | mariadb | Generated at deploy |
| MYSQL_USER | mariadb | Generated at deploy |
| TZ | uptime-kuma | Preset by the template |
Ports and volumes
- Ports
- 3001
- Volumes
- 2 named mounts: uptime_kuma_mariadb_data -> /var/lib/mysql, uptime_kuma_mariadb_app_data -> /app/data
Uptime Kuma (MariaDB) FAQ
How much memory does Uptime Kuma (MariaDB) need?
The catalog lists about 512 MiB of memory for Uptime Kuma (MariaDB) across its 2 services.
Does Uptime Kuma (MariaDB) run on arm64?
For Uptime Kuma (MariaDB), an arm64 image is published; amd64 is image published.
What licence is Uptime Kuma (MariaDB) under?
Uptime Kuma (MariaDB) is licensed under MIT, which is permissive, with few conditions on reuse.
Does Uptime Kuma (MariaDB) need configuration before it starts?
No. The template fills in its own defaults and generates secrets at deploy time.
Which database does Uptime Kuma (MariaDB) bundle?
The template includes MySQL, running as its own service.
Which ports does Uptime Kuma (MariaDB) use?
Uptime Kuma (MariaDB) listens on port 3001 inside the stack.
Where does Uptime Kuma (MariaDB) keep its data?
In named volumes: uptime_kuma_mariadb_data mounted at /var/lib/mysql and uptime_kuma_mariadb_app_data mounted at /app/data.
Can I deploy Uptime Kuma (MariaDB) 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 Uptime Kuma (MariaDB), 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 mariadb:11, louislam/uptime-kuma:2 is what you deploy there.