FUSE and Docker

Users and FUSE

Because of the nature of FUSE systems, only the user who starts a FUSE program will be able to read the files mounted. This can be changed by editing a config file (reference) on the machine to allow_others, but be warned that there are security implications to be considered: https://github.com/libfuse/libfuse#security-implications. Generally we don't recommend this option. It is best to create a user one intends on using to mount fusera and to invoke the tools that will interact with fusera. This avoids this issue.

But what about using Docker containers which run as different users?

If a user desires to run tools inside a docker container on files inside fusera's file system, they still both need to be operating as the same user. This is best done by doing everything from the docker container.

The process would be something like starting the container with a volume already mapped to the folder fusera will be mounted to. Then, start a container that is configured with fusera and the tools installed. One can either have it be part of the container setup to mount fusera to the volume or go into the container on their own and manually mount. Then, the same user in the container would have mounted fusera and be invoking the tools that would be used with fusera's file system. This allows for a clean and safe way for users to utilize docker and fusera.