svenvg93 6b83ca0713 fix(agent): make package update checks work as the sandboxed agent user
The agent runs as the beszel user under ProtectSystem=strict, so package
managers that write temp, cache or log files failed with only
"exit status 1" in the log.

- Include the command's stderr in check errors.
- dnf5 (Fedora 41+): point XDG_STATE_HOME and XDG_CACHE_HOME into the
  agent's data dir. They default to $HOME, which is /nonexistent for
  the beszel user. With -C, dnf5 still reads the system metadata cache.
- zypper: keep the solv cache in the data dir with --solv-cache-dir,
  since the agent user cannot rebuild it in /var/cache/zypp.
- pacman: read the system sync databases with pacman -Qu instead of
  syncing a private copy with checkupdates. This drops the
  pacman-contrib and fakeroot dependencies and pacman's download
  sandbox, which fails in containers without Landlock. Like the other
  managers, it never refreshes the databases itself.
- install-agent.sh, Debian unit: add PrivateTmp=yes. The script adds it
  to existing units too when re-run. dnf4 (Rocky, Alma) and zypper keep
  temporary files in /var/tmp, which ProtectSystem=strict makes
  read-only. dnf4 hardcodes /var/tmp, so the agent cannot work around
  it. apt does not need it; the Debian unit gets it so both units stay
  the same.
2026-10-05 08:32:23 +02:00
2026-10-02 13:13:54 -04:00
2026-10-02 12:31:52 -04:00
2024-07-20 17:52:51 -04:00
2026-10-02 13:13:54 -04:00
2026-10-01 11:30:38 -04:00
2026-10-01 11:30:38 -04:00
2025-09-11 12:45:43 -04:00
2024-07-21 22:30:53 -04:00
2026-09-19 12:11:10 -04:00

Beszel

Beszel is a lightweight server monitoring platform that includes Docker statistics, historical data, and alert functions.

It has a friendly web interface, simple configuration, and is ready to use out of the box. It supports automatic backup, multi-user, OAuth authentication, and API access.

agent Docker Image Size hub Docker Image Size MIT license Crowdin

Screenshot of Beszel dashboard and system page, side by side. The dashboard shows metrics from multiple connected systems, while the system page shows detailed metrics for a single system.

Features

  • Lightweight: Smaller and less resource-intensive than leading solutions.
  • Simple: Easy setup with little manual configuration required.
  • Alerts: Configurable alerts for most metrics. Supports many notification services.
  • Docker stats: Tracks CPU, memory, and network usage history for each container.
  • Network monitoring: Monitor response time and interruptions directly from agents.
  • S.M.A.R.T.: Disk health data and notifications on drive failure.
  • Multi-user: Users manage their own systems. Admins can share systems across users.
  • OAuth / OIDC: Supports many OAuth2 providers. Password auth can be disabled.
  • Automatic backups: Save to and restore from disk or S3-compatible storage.

Architecture

Beszel consists of two main components: the hub and the agent.

  • Hub: A web application built on PocketBase that provides a dashboard for viewing and managing connected systems.
  • Agent: Runs on each system you want to monitor and communicates system metrics to the hub.

Getting started

The quick start guide and other documentation is available on our website, beszel.dev. You'll be up and running in a few minutes.

Screenshots

Dashboard System page Notification Settings

Supported metrics

  • CPU usage - Host system and Docker / Podman containers.
  • Memory usage - Host system and containers. Includes swap and ZFS ARC.
  • Disk usage - Host system. Supports multiple partitions and devices.
  • Disk I/O - Host system. Supports multiple partitions and devices.
  • Network usage - Host system and containers.
  • Load average - Host system.
  • Temperature - Host system sensors.
  • Fan speed - Host system sensors (Linux, via /sys/class/hwmon).
  • GPU usage / power draw - Nvidia, AMD, and Intel.
  • Battery charge - Host system and some peripherals.
  • Containers - Status and metrics of all running Docker / Podman containers.
  • S.M.A.R.T. - Host system disk health (includes eMMC wear/EOL and Linux mdraid array health via sysfs when available).
  • ZFS - Pool capacity, usage, health, I/O throughput, scrub status, and per-dataset usage.

Help and discussion

Please search existing issues and discussions before opening a new one. I try my best to respond, but may not always have time to do so.

Bug reports and feature requests

Bug reports and feature requests can be posted on GitHub issues.

Support and general discussion

Support requests and general discussion can be posted on GitHub discussions or the community-run Matrix room: #beszel:matrix.org.

License

Beszel is licensed under the MIT License. See the LICENSE file for more details.

S
Description
No description provided
Readme MIT
135 MiB
Languages
Go 91.9%
TypeScript 4.1%
Shell 2.1%
PowerShell 1.4%
CSS 0.2%
Other 0.2%