Self-host VictoriaMetrics with Levelrail
A fast, resource-frugal time-series database that speaks the Prometheus query and remote-write APIs. Has no authentication, so point Prometheus-style senders at victoriametrics:8428 from other services in this project, or attach a domain only behind Basic Auth. Not published on the host.
- AuthorVictoriaMetrics
- LicenceApache-2.0
- Memory512 MiB
- Archarm64
- Services1
How to self-host VictoriaMetrics
-
Pull the images
One image is pulled on your server.
Show images
victoriametrics/victoria-metrics:v1.152.0
-
Create the app
One service starts in a single Compose app, with 1 named volume mount for your data, on port 8428.
-
Fill in the secrets
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.
VictoriaMetrics requirements
- Memory
- About 512 MiB
- Architectures
- amd64 image published, arm64 image published
- Ports
- 8428
- 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 VictoriaMetrics. 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 VictoriaMetrics docs page.
Deploy VictoriaMetrics your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy VictoriaMetrics from the CLI
levelrail-cli templates deploy victoriametrics --name my-victoriametrics Deploy VictoriaMetrics with the API
curl -X POST -H "Authorization: Bearer $TOKEN" \
https://levelrail.example.com/api/v1/service-templates/victoriametrics/deploy VictoriaMetrics configuration
VictoriaMetrics services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| victoriametrics | victoriametrics/victoria-metrics:v1.152.0 | 8428 | victoriametrics_data -> /storage |
VictoriaMetrics environment variables
The catalog lists no environment variables for this template.
Ports and volumes
- Ports
- 8428
- Volumes
- 1 named mount: victoriametrics_data -> /storage
VictoriaMetrics FAQ
How much memory does VictoriaMetrics need?
The catalog lists about 512 MiB of memory for VictoriaMetrics.
Does VictoriaMetrics run on arm64?
For VictoriaMetrics, an arm64 image is published; amd64 is image published.
What licence is VictoriaMetrics under?
VictoriaMetrics is licensed under Apache-2.0, which is permissive, with few conditions on reuse.
Does VictoriaMetrics need configuration before it starts?
No. The template fills in its own defaults.
Which ports does VictoriaMetrics use?
VictoriaMetrics listens on port 8428 inside the stack.
Where does VictoriaMetrics keep its data?
In a named volume: victoriametrics_data mounted at /storage.
Can I deploy VictoriaMetrics on Dokploy or Dokku?
The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list has an entry with the id victoriametrics for this app, so check that entry as well. Dokku deploys container images with its own commands, so the pinned image victoriametrics/victoria-metrics:v1.152.0 is what you deploy there.