Is there a way to keep it running as root within the container? Would make setup easier for rootless podman containers .

[eduardhc]

Hi, and thank you for keeping this project alive, it is such a nice tool!

I was wondering is there is way to keep internal daemon running as "root" inside the container, instead of forcing it to use an unprivileged user (1000:1000) instead. As per the documentation, this was the behaviour in 1.2, but it's been changed in v1.3 (IIRC).

For context: running the container daemon using an unprivileged internal account is always usually a good idea on Docker setups, but it might complicate things a bit when using podman from a user account (this is, what is known as a "rootless" setup). In Docker setups, it's trivial to map the container user to a local account, so it can access the files to be shared. In Podman world, however, this is a bit more complicated because that "container local user" is mapped to a sub-account of the user running the container, and assigned an (almost) random UID/GID which makes dealing with file permissions trickier.

A good workaround to this is to keep running the container process as root, because that "local root" of the container is mapped actually to the user account running the container (and not to the actual host's root), so file permission mapping is trivial. However, this doesn't seem to be possible anymore with FileBrowser Quantum.

Any chances to bring old behaviour back? Even as a disabled-by-default option, of course).

Kind regards.

[gtsteffaniak]

you mentioned the docs, so I assume you have seen and read this.

The only change was the default user is now filebrowser (1000:1000) instead of root. You can always manually set it back to root if you need to via user: root. Perhaps I am missing something, wouldn't that keep the functionality the same for you?

[eduardhc]

Ok, thanks for the answer, I'll give it a try later today. The podman Kube-style YAML file I'm using does not actually feature the "user: " keyword, but I think the "runAsUser" directive will be the closest replacement.