-
Notifications
You must be signed in to change notification settings - Fork 208
Description
Description
I'm running Filebrowser in a rootless container on OpenShift, where the container does not have permission to execute chown.
When uploading a file, the upload succeeds and the file is written to disk, but Filebrowser attempts to change file ownership, which fails due to OpenShift security constraints. This triggers an upload alert/error even though the file upload is successful.
I would like to request a way to disable the chown operation during file upload, ideally via an environment variable (e.g. FB_DISABLE_CHOWN=true).
This would allow rootless deployments on OpenShift / Kubernetes to run without unnecessary warnings.
I am willing to contribute a PR if this feature aligns with the project's direction — just want to confirm there is not already a config option for this.
Expected behaviour
File uploads should succeed without displaying warnings in environments where chown is not permitted.
When a dedicated option is enabled, Filebrowser should skip chown on uploaded files.
What is happening instead?
- File is uploaded successfully ✅
- Filebrowser tries to run
chown❌ - Upload UI shows an alert / warning
⚠️ - Logs include permission denied errors related to
chown
(Note: I can provide exact logs once needed — their content relates to permission denied syscall on chown)
Additional context
This applies to rootless environments such as:
- OpenShift restricted SCC
- Podman rootless mode
- Kubernetes with security hardening where only
fsGroupis allowed
Skipping chown is acceptable in my case because the Kubernetes security context already manages file permissions.
I am also preparing a Helm chart for Filebrowser deployment on OpenShift and can share it as reference.
How to reproduce?
- Deploy Filebrowser on OpenShift using a rootless container (restricted SCC)
- Attempt to upload a file via the web UI
- File uploads, but UI shows an error/warning
- Logs show
chownpermission denied messages
Files
I will share the Helm chart for the pilot deployment when needed.
(Upload logs available if required)
Metadata
Metadata
Assignees
Labels
Projects
Status