DAM/ts-CATALOG
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs(catalog): mark uptime-kuma as verified (2026-08-02)

Browse Source 
- 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.
This commit is contained in:
peskyadmin
2026-08-02 20:13:35 -04:00
parent 911dff3fe0
commit b4e55acfc1
1 changed files with 9 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
catalog.yaml
View File

@@ -456,11 +456,19 @@ apps:
db: sqlite db: sqlite
architecture: single architecture: single
first_run: setup_wizard first_run: setup_wizard
test_status: untested test_status: verified
test_date: 2026-08-02
repo: https://gitea.damconsulting.llc/dam/ts-uptime-kuma repo: https://gitea.damconsulting.llc/dam/ts-uptime-kuma
notes: | notes: |
Single container, SQLite-backed. No external DB needed. Single container, SQLite-backed. No external DB needed.
Drop the db service entirely. 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 - service: vaultwarden
display_name: Vaultwarden display_name: Vaultwarden