Hardening a Beszel Hub Without Giving It the Docker Socket
It's 3:00 AM. Your monitoring dashboard just got compromised through an unpatched dependency. Five minutes later, the attacker has root on every Docker host because you mounted /var/run/docker.sock into the hub container six months ago to "make container metrics work." This is not a theoretical exercise—it's the inevitable outcome of treating monitoring infrastructure as low-risk simply because it's internal.
Evaluating henrygd/beszel , the architectural boundary I care about is straightforward: the hub stores history and serves the dashboard; agents collect measurements from monitored machines. Docker statistics belong at the collection boundary, not inside the dashboard container. The developer pain point is granting host-level authority simply to display metrics.…