Self-host Node Exporter with Levelrail
A Prometheus exporter for hardware and OS metrics of the host it runs on. It serves plain metrics at /metrics for a Prometheus server to scrape.
- Authorprometheus
- LicenceApache-2.0
- Memory64 MiB
- Services1
How to self-host Node Exporter
-
Pull the images
One image is pulled on your server.
Show images
prom/node-exporter:v1.12.1
-
Create the app
One service starts in a single Compose app, on port 9100.
-
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.
After the first start
- Add node-exporter:9100 as a scrape target in your Prometheus config. The page serves metrics only.
Node Exporter requirements
- Memory
- About 64 MiB
- Architectures
- amd64 unknown, arm64 unknown
- Ports
- 9100
- 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 Node Exporter. 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 Node Exporter docs page.
Deploy Node Exporter your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy Node Exporter from the CLI
levelrail-cli templates deploy node-exporter --name my-node-exporter Deploy Node Exporter with the API
curl -X POST -H "Authorization: Bearer $TOKEN" \
https://levelrail.example.com/api/v1/service-templates/node-exporter/deploy Node Exporter configuration
Node Exporter services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| node-exporter | prom/node-exporter:v1.12.1 | 9100 | none |
Node Exporter environment variables
The catalog lists no environment variables for this template.
Ports and volumes
- Ports
- 9100
- Volumes
- none
Node Exporter FAQ
How much memory does Node Exporter need?
The catalog lists about 64 MiB of memory for Node Exporter.
Does Node Exporter run on arm64?
For Node Exporter, arm64 support is not confirmed; amd64 is unknown.
What licence is Node Exporter under?
Node Exporter is licensed under Apache-2.0, which is permissive, with few conditions on reuse.
Does Node Exporter need configuration before it starts?
No. The template fills in its own defaults.
Which ports does Node Exporter use?
Node Exporter listens on port 9100 inside the stack.
Can I deploy Node Exporter 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 Node Exporter, 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 prom/node-exporter:v1.12.1 is what you deploy there.