filebrowser v2.63.13 was 0/1 because v2.63.x changed the default config-file lookup from /.filebrowser.json (where our ConfigMap is mounted) to /config/settings.json (where it's not). It started with built-in defaults (port 80) so the readiness probe on 8080/health timed out. Pass -c /.filebrowser.json explicitly.
filebrowser v2.63.13 was 0/1 because v2.63.x changed the default config-file lookup from `/.filebrowser.json` (where our ConfigMap is mounted) to `/config/settings.json` (where it's not). It started with built-in defaults (port 80) so the readiness probe on 8080/health timed out. Pass `-c /.filebrowser.json` explicitly.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
The previous PR pinned filebrowser to v2.63.13 + runAsUser:0 which
solved the PVC permission issue, but the pod was still 0/1 Ready
because v2.63.x changed the default config-file lookup path:
Old (v2-alpine): /.filebrowser.json (matched our existing mount)
New (v2.63.13) : /config/settings.json (NOT mounted in this pod)
So the new image ran with its built-in defaults (port 80, in-memory
db), and the readiness probe on 8080/health timed out.
Fix: pass `args: ["-c", "/.filebrowser.json"]` so filebrowser uses the
ConfigMap we already mount there. No volumeMount changes needed.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
admin
merged commit 7b545c1ec7 into main2026-06-06 14:22:06 +02:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
filebrowser v2.63.13 was 0/1 because v2.63.x changed the default config-file lookup from
/.filebrowser.json(where our ConfigMap is mounted) to/config/settings.json(where it's not). It started with built-in defaults (port 80) so the readiness probe on 8080/health timed out. Pass-c /.filebrowser.jsonexplicitly.🤖 Generated with Claude Code