1.9 KiB
1.9 KiB
| title | description | published | date | tags | editor | dateCreated |
|---|---|---|---|---|---|---|
| Audit - firefox.yaml | Gremlin audit report 2026-04-03 | true | 2026-04-03T02:51:09.611Z | gremlin,audit | markdown | 2026-04-03T02:51:09.611Z |
Audit Report — firefox.yaml
Date: 2026-04-03
File: swarm/firefox.yaml
Type: Docker Swarm
Verdict: FAIL
SWARM AUDIT
-
Homepage labels:
homepage.group: Remote Access (PASS)homepage.name: Firefox (PASS)homepage.icon: firefox.png (PASS)homepage.href: https://firefox.netgrimoire.com (PASS)homepage.description: Remote Browser (PASS)
-
Uptime Kuma labels:
- No Uptime Kuma labels found in the provided YAML file (FAIL). Ensure that any services running on this host have proper Uptime Kuma labels for visibility.
-
Caddy labels on exposed services:
caddy=firefox.netgrimoire.com(PASS)caddy.reverse_proxy=http://firefox:5800(PASS)
-
Placement constraints:
- No placement constraints found in the provided YAML file (FAIL). Ensure that any critical services have proper placement constraints to meet availability requirements.
-
Volumes use /DockerVol/ path convention:
- Volume path
/data/nfs/znas/Docker/firefoxdoes not follow the/DockerVol/<service>convention (FAIL). Volumes should be placed in a directory following this naming scheme for consistency and ease of management.
- Volume path
-
Network references external netgrimoire overlay:
- Network
netgrimoireis referenced correctly and marked as external (PASS).
- Network
VERDICT: FAIL
- The YAML file lacks Uptime Kuma labels, which are essential for monitoring the status of services.
- No placement constraints are defined, which can lead to issues with service availability and redundancy.
- Volumes do not follow the recommended path convention, which may cause confusion and difficulty in managing storage resources.