Vigilant-Vole ghcr.io/ferdinand99/vigilant-vole:latest https://github.com/Ferdinand99/Vigilant-Vole/pkgs/container/vigilant-vole bridge sh false https://github.com/Ferdinand99/Vigilant-Vole/issues https://github.com/Ferdinand99/Vigilant-Vole Vigilant Vole is a lightweight, self-hosted uptime monitor written in Rust - an Uptime Kuma alternative in one small image (about 18 MB compressed, a few MB of RAM). Monitors: HTTP(S), keyword, JSON query, TCP port, ping, DNS, push/heartbeat, Docker container, WebSocket, TLS certificate and domain expiry, NTP and Steam game servers, plus groups. Alerts go to 24 notification services (Discord, Slack, Telegram, email, ntfy, Gotify, Pushover, Teams, Matrix, PagerDuty and more), and Apprise covers 90+ others, with retries, reminders, escalation and flap detection. Also included: public status pages with custom domains, incidents and badges; maintenance windows; multi-user roles with two-factor login; remote probe agents that confirm an outage from another network before alerting; Docker label auto-discovery; a REST API, config as code (YAML/JSON) and an Uptime Kuma importer; Prometheus metrics with Kuma-compatible names. English and Norwegian interface. Setup: open the WebUI after the first start and create the admin account. Everything lives in one SQLite file under /data (appdata). Map the Docker socket only if you want Docker container monitors or label discovery. Network:Management Tools:Utilities http://[IP]:[PORT:3001]/ https://raw.githubusercontent.com/Ferdinand99/unraid-templates/main/templates/vigilant-vole.xml https://raw.githubusercontent.com/Ferdinand99/Vigilant-Vole/main/assets/unraid-icon.png --cap-add=NET_RAW For Docker container monitors and label discovery, map the Docker socket below. The container picks up the socket's group by itself. 3001 /mnt/user/appdata/vigilant-vole 99 100 0 info