Self-host Netdata with Levelrail

Per-second infrastructure metrics with zero configuration and a live dashboard out of the box.

  • Authornetdata
  • LicenceGPL-3.0-or-later
  • Memory512 MiB
  • Archarm64
  • Services1

How to self-host Netdata

  1. Pull the images

    One image is pulled on your server.

    Show images
    • netdata/netdata:v2.11.1
  2. Create the app

    One service starts in a single Compose app, with 3 named volume mounts for your data, on port 19999.

  3. Fill in the secrets

    You do not have to fill in anything.

  4. Open it

    Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.

Netdata requirements

Memory
About 512 MiB
Architectures
amd64 image published, arm64 image published
Ports
19999
Domain
Optional, an sslip.io address is used without one
Settings
none to fill in
License
GPL-3.0-or-later, copyleft 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 19999 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 Netdata. 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 Netdata docs page.

Deploy Netdata your way

Every format below deploys the same pinned images. Pick the one that fits how you work.

Deploy Netdata from the CLI

levelrail-cli templates deploy netdata --name my-netdata

Deploy Netdata with the API

Create a token in the dashboard first. This one-click route deploys it as a trial app you can keep or remove.

curl -X POST -H "Authorization: Bearer $TOKEN" \
  https://levelrail.example.com/api/v1/service-templates/netdata/deploy

Netdata configuration

Netdata services

ServiceImagePortsVolumes
netdata netdata/netdata:v2.11.1 19999 netdata_config -> /etc/netdatanetdata_lib -> /var/lib/netdatanetdata_cache -> /var/cache/netdata

Netdata environment variables

The catalog lists no environment variables for this template.

Ports and volumes

Ports
19999
Volumes
3 named mounts: netdata_config -> /etc/netdata, netdata_lib -> /var/lib/netdata, netdata_cache -> /var/cache/netdata

Netdata FAQ

How much memory does Netdata need?

The catalog lists about 512 MiB of memory for Netdata.

Does Netdata run on arm64?

For Netdata, an arm64 image is published; amd64 is image published.

What licence is Netdata under?

Netdata is licensed under GPL-3.0-or-later, which is copyleft, so changes you distribute must be shared under the same terms.

Does Netdata need configuration before it starts?

No. The template fills in its own defaults.

Which ports does Netdata use?

Netdata listens on port 19999 inside the stack.

Where does Netdata keep its data?

In named volumes: netdata_config mounted at /etc/netdata, netdata_lib mounted at /var/lib/netdata and netdata_cache mounted at /var/cache/netdata.

Can I deploy Netdata 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 netdata for this app, so check that entry as well. Dokku deploys container images with its own commands, so the pinned image netdata/netdata:v2.11.1 is what you deploy there.

levelrail-cli templates deploy netdata --name my-netdata