Dockhand vulnerability scans: warn about critical findings, with a setting to turn it off
Reads what Dockhand's scans have already stored (never starts one) every 15 minutes and raises a warning per Docker host with critical findings. Unknown counts and stale readings are held, not treated as clean. Settings -> Notifications has a switch (on by default); the Docker page shows counts, scan coverage and the critical findings; /metrics and docs updated. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
65214f6f0f
commit
5a2b320175
25 files changed
+8527
-12
No files matched your search
@@ -127,8 +127,10 @@ All modules from the original plan are built:
|
||||
manages (one credential covers all of them), with
|
||||
start/stop/restart actions, a host filter, image-update status per
|
||||
container (from Dockhand's own cached update check, plus a button
|
||||
to trigger a fresh one), and a live running/total widget (with an
|
||||
updates-available count).
|
||||
to trigger a fresh one), a live running/total widget (with an
|
||||
updates-available count), and the **vulnerabilities** Dockhand's own
|
||||
scans found per host (critical ones listed; a warning is raised for
|
||||
critical ones, and it can be switched off).
|
||||
- **Uptime Kuma** — every monitor's status (up/down/pending/maintenance),
|
||||
response time, and 24h/30d uptime, with certificate days remaining where
|
||||
applicable. Each monitor is matched to one of your servers when its
|
||||
|
||||
Reference in new issue
Block a user