Self-host Prometheus with Levelrail
VerifiedA metrics time-series database and alerting engine built for pull-based scraping.
- Authorprometheus
- LicenceApache-2.0
- Memory512 MiB
- Archarm64
- Services1
How to self-host Prometheus
-
Pull the images
One image is pulled on your server.
Show images
prom/prometheus:v2.54.1
-
Create the app
One service starts in a single Compose app, with 1 named volume mount for your data, on port 9090.
-
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.
Prometheus requirements
- Memory
- About 512 MiB
- Architectures
- amd64 image published, arm64 tested
- Ports
- 9090
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- Apache-2.0, permissive license
- Verified. Verified on arm64 with image tag v2.54.1. Our CI ran this exact image version and it answered on its health path. Evidence
- Host ports. It publishes port 9090 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 Prometheus. 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 Prometheus docs page.
Deploy Prometheus your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy Prometheus from the CLI
levelrail-cli templates deploy prometheus --name my-prometheus Deploy Prometheus with the API
curl -X POST -H "Authorization: Bearer $TOKEN" \
https://levelrail.example.com/api/v1/service-templates/prometheus/deploy Prometheus configuration
Prometheus services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| prometheus | prom/prometheus:v2.54.1 | 9090 | prometheus_data -> /prometheus |
Prometheus environment variables
The catalog lists no environment variables for this template.
Ports and volumes
- Ports
- 9090
- Volumes
- 1 named mount: prometheus_data -> /prometheus
Prometheus FAQ
How much memory does Prometheus need?
The catalog lists about 512 MiB of memory for Prometheus.
Does Prometheus run on arm64?
For Prometheus, arm64 is tested; amd64 is image published.
What licence is Prometheus under?
Prometheus is licensed under Apache-2.0, which is permissive, with few conditions on reuse.
Does Prometheus need configuration before it starts?
No. The template fills in its own defaults.
Which ports does Prometheus use?
Prometheus listens on port 9090 inside the stack.
Where does Prometheus keep its data?
In a named volume: prometheus_data mounted at /prometheus.
Can I deploy Prometheus 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 prometheus for this app, so check that entry as well. Dokku deploys container images with its own commands, so the pinned image prom/prometheus:v2.54.1 is what you deploy there.