Netdata
Container
Troubleshoot slowdowns and anomalies in your infrastructure with thousands of per-second metrics, meaningful visualizations, and insightful health alarms with zero configuration.
Image details
Source details
Configuration
TypeContainerlinuxnetdata/netdata:latest19999:19999/tcp/etc/netdata : /portainer/Files/AppData/Config/netdata/netdataconfig/var/lib/netdata : /portainer/Files/AppData/Config/netdata/netdatalib/host/etc/passwd:ro : /etc/passwd/host/etc/group:ro : /etc/group/host/proc:ro : /proc/host/sys:ro : /sys/host/etc/os-release:ro : /etc/os-releaseDOCKER_USR=1000DOCKER_GRP=1000unless-stoppedTemplate by novaspirit
Report issueNotes
Check our Github page: https://github.com/pi-hosted/pi-hosted
Official Webpage: https://www.netdata.cloud/
Official Docker Documentation: https://learn.netdata.cloud/docs/agent/packaging/docker
Documentation is Available here.
Standalone Install
Select an install method, to see config/commands for deploying Netdata
Install on Portainer
Import all app templates into your Portainer instance, for easy 1-click deploys
- Ensure both Docker and Portainer are installed, and up-to-date
- Log into your Portainer web UI
- Under Settings → App Templates, paste the below URL
- Head to Home → App Templates, and the list of apps will show up
- Select Netdata, fill in any config options, and hit Deploy
Template Import URL
https://raw.githubusercontent.com/Lissy93/portainer-templates/main/templates.json
Show Me
More install options in our documentation, or see netdata/netdata for app-specific guidance.
Netdata
Full-stack observability: the AI SRE that learns your stack!Metrics · Logs · Traces · Flows · Topology Infrastructure · APM · NPM · DBM · RUM · Synthetics · Cloud · AI SRE OpenTelemetry · SNMP · NetFlow/IPFIX/sFlow · IPMI · Redfish · 2,000+ integrations
Netdata is a full-stack observability platform: infrastructure, application performance monitoring (OpenTelemetry traces, service maps, RED), digital experience (real user monitoring, synthetic monitoring), network performance monitoring (SNMP, topology, NetFlow/IPFIX/sFlow, traps, BGP), databases, logs and cloud, with AI troubleshooting over all of it.
Netdata Agents collect, store and analyze data where it is generated, per second, with machine learning anomaly detection on every metric. Netdata Parents and Netdata Cloud combine them into one view, without centralizing the data. Netdata scales from a single node to 100,000+ nodes, and its Agent is open source.
- Everything, every second: per-second collection, with about 0.6 bytes per sample on disk.
- Machine learning on every metric: clusters of anomalies reveal dependencies that would otherwise go unnoticed, show how problems cascade across systems, networks and applications, and surface the actual impact of failures.
- AI SRE: automated root cause and impact analysis, plus MCP servers that give any AI assistant the same evidence.
- Nothing to build first: auto-discovery, ready-made dashboards and alerts, no query language required.
Run the Netdata Agent container
docker run -d --name=netdata \
--pid=host \
--network=host \
-v netdataconfig:/etc/netdata \
-v netdatalib:/var/lib/netdata \
-v netdatacache:/var/cache/netdata \
-v /:/host/root:ro,rslave \
-v /etc/passwd:/host/etc/passwd:ro \
-v /etc/group:/host/etc/group:ro \
-v /etc/localtime:/etc/localtime:ro \
-v /proc:/host/proc:ro \
-v /sys:/host/sys:ro \
-v /etc/os-release:/host/etc/os-release:ro \
-v /var/log:/host/var/log:ro \
-v /var/run/docker.sock:/var/run/docker.sock:ro \
-v /run/dbus:/run/dbus:ro \
--restart unless-stopped \
--cap-add SYS_PTRACE \
--cap-add SYS_ADMIN \
--security-opt apparmor=unconfined \
netdata/netdataThen open
http://NODE:19999. Docker Compose, GPU, TLS proxy, socket proxy and rootless setups, the privileges and mounts each feature needs, and environment variables are in the Docker installation guide.Tags
| Tag | Description |
|---|---|
stable | The most recently published stable build. |
edge | The most recently published nightly build, usually updated daily around 01:00 UTC. |
latest | The most recently published build, stable or nightly. Docker uses it when no tag is given. |
vX.Y.Z | A full release version, for example v2.12.0. |
vX.Y | Major and minor version; moves with each matching patch release. |
vX | Major version only. |
Links
Serve Netdata on your own domain behind Caddy, Nginx or Traefik. Fill in your domain and copy the result. It's a starting point, some apps need their own base URL or extra headers set too.
Proxying netdata.example.com to http://netdata:19999
Add this to your Caddyfile
netdata.example.com {
reverse_proxy http://netdata:19999
}Check the logs first
Nine times out of ten the logs tell you exactly what went wrong.
- In Portainer, go to Containers, click the container, then Logs. Or run
docker logs netdata - Exit codes help too:
137means killed, usually out of memory.126or127means the command inside the image is broken.
Port already in use
If deployment fails with "Bind for 0.0.0.0:19999 failed: port is already allocated", something else on your server is using that port.
- Find what's using it:
sudo ss -tlnp | grep :19999 - Stop the other service, or pick a different host port. In
19999:19999only the left number is yours to change, the right one belongs to the app.
Running but the page won't load
The container is up but nothing appears in your browser.
- Use your server's real IP:
http://your-server-ip:19999. The 0.0.0.0 link Portainer shows isn't a real address. - Give it a minute after first deploy, netdata can take a while to initialise.
- Make sure your firewall allows the port, e.g.
sudo ufw allow 19999
Permission denied on volumes
If the logs show "permission denied", the app can't write to its data folder on the host.
- Fix the ownership:
sudo chown -R 1000:1000 /portainer/Files/AppData/Config/netdata/netdataconfig(and the same for the other mapped folders)
Image won't pull
Test the pull directly on the host: docker pull netdata/netdata:latest
- "manifest unknown" means the tag no longer exists. This template uses
latest, so try pinning a specific version instead. - "toomanyrequests" is the Docker Hub rate limit. Log in with
docker loginto raise it. - "no space left on device" means a full disk. Reclaim space with
docker system prune
"exec format error"
This means the image was built for a different CPU architecture than your server.
- This image supports:
amd64, arm64, arm/v7, 386, ppc64le - Check yours with
uname -m: x86_64 is amd64, aarch64 is arm64. Raspberry Pi and other ARM boards are the usual culprits.
Container keeps restarting
The unless-stopped restart policy relaunches the app after every crash, so the real error can scroll past.
- Check the logs right after a restart, the last few lines before it died are the useful ones.
- Get the exit code with
docker inspect netdata --format '{{.State.ExitCode}}' - Still stuck? Redeploy once with the restart policy set to
noso the failure stays visible.
Raise an issue
Found something which isn't working as it should? Here's how to report it.
- Bug within the app: Open an issue on netdata/netdata
- Template not working: Open an issue on novaspirit/pi-hosted
- This website not working: Open an issue on lissy93/portainer-templates
A single container
Netdata runs as one container, the simplest kind of app here. Just the one image to pull and nothing else wired up alongside it.
The app image
An image is the app packed up ready to go, everything Netdata needs bundled into one download. This template pulls netdata/netdata:latest, which Docker fetches once (about 292 MB) and then starts your own copy from.
Where the image comes from
Docker pulls its images from registries, public libraries of ready-built apps. Netdata's comes from Docker Hub, published by netdata.
Version tags
The bit after the colon in the image name is the version tag. Here it's latest, which always points at the newest build, so a redeploy can bump you to a newer release without you asking. Newest right now is v2.13.0. Pin a specific tag if you would rather stay on one version.
Which machines it runs on
Every image is built for particular CPU types. This one ships for amd64, arm64, arm/v7, 386, ppc64le, so it runs on both regular x86 servers and ARM boards like a Raspberry Pi.
Ports
A port is the door the app answers on. A mapping like 19999:19999 means it's reachable on port 19999 of your server, where the left number is yours to change and the right one belongs to the app. It opens:
19999:19999
Volumes
A volume is where Netdata keeps its files so they survive an update or a restart. Without one, anything it saves would sit inside the container and vanish the moment it's recreated. This template mounts:
/etc/netdatafrom/portainer/Files/AppData/Config/netdata/netdataconfigon the host/var/lib/netdatafrom/portainer/Files/AppData/Config/netdata/netdatalibon the host/host/etc/passwd:rofrom/etc/passwdon the host/host/etc/group:rofrom/etc/groupon the host/host/proc:rofrom/procon the host/host/sys:rofrom/syson the host/host/etc/os-release:rofrom/etc/os-releaseon the host
Environment variables
Environment variables are the settings you hand over when you deploy, things like a password or a timezone. Netdata takes 2 of them, all with defaults you can leave alone or tweak:
DOCKER_USR, defaults to1000DOCKER_GRP, defaults to1000
Restart policy
The restart policy here is unless-stopped, so Docker restarts Netdata after a crash or reboot, but leaves it off when you stop it on purpose. You can change this on the deploy screen. The choices are no (never restart), on-failure (only after a crash), unless-stopped (restart unless you stop it), and always (bring it back no matter what).
Networking
Nothing custom is set, so Netdata sits on Docker's default bridge network: its own private space that reaches the outside world only through the ports it publishes.
Container name
Once it's deployed, Portainer names the container netdata. That's what you'll spot in the containers list and use in commands like docker logs netdata.
Platform
The platform is linux, the kind of system the container is built to run on. Docker and Portainer handle this on a normal Linux server.
Open source license
Netdata is open source, released under the GPL-3.0 license. In plain terms the code is out in the open, so you're free to run it and change it to fit what you need.
Portainer app templates
Zooming out, this whole page comes from a Portainer app template: a short recipe telling Portainer how to set Netdata up. Add the template list to Portainer once, then deploying Netdata is a click rather than a wall of config.