From b4e55acfc10ae4181e771efc5379140687ccbfb0 Mon Sep 17 00:00:00 2001
From: peskyadmin <peskyadmin@peskyadmins-Mac-mini.local>
Date: Sun, 2 Aug 2026 20:13:35 -0400
Subject: [PATCH] docs(catalog): mark uptime-kuma as verified (2026-08-02)

- test_status: verified
- Add prominent gotcha: USE NAMED VOLUMES, not bind mounts
  macOS Docker Desktop has gRPC-FUSE UID remapping that breaks
  chown calls inside containers. Bind mount chown permissions
  cannot be resolved cleanly. Named volumes work identically
  on macOS and Linux without any permission workarounds.
---
 catalog.yaml | 10 +++++++++-
 1 file changed, 9 insertions(+), 1 deletion(-)

diff --git a/catalog.yaml b/catalog.yaml
index 8941cd2..26a32d5 100644
--- a/catalog.yaml
+++ b/catalog.yaml
@@ -456,11 +456,19 @@ apps:
     db: sqlite
     architecture: single
     first_run: setup_wizard
-    test_status: untested
+    test_status: verified
+    test_date: 2026-08-02
     repo: https://gitea.damconsulting.llc/dam/ts-uptime-kuma
     notes: |
       Single container, SQLite-backed. No external DB needed.
       Drop the db service entirely.
+      Data volume path is /app/data/uptime-kuma (NOT /data).
+      Only net_admin needed (not sys_module).
+      USE NAMED VOLUMES (NOT BIND MOUNTS) FOR DATA - macOS Docker Desktop
+      has gRPC-FUSE UID remapping that breaks chown inside containers.
+      Named volumes work identically on macOS + Linux.
+      TS_EXTRA_ARGS=--login-server=${TS_LOGIN_SERVER} required for Headscale.
+      tailscale/config volume mount required for serve.json.
 
   - service: vaultwarden
     display_name: Vaultwarden