Your comments

Not sure if it is due to a reboot of my server, but suddenly tonight the @Home folder in Nextcloud shows all my files (even rbind mounts I made, instead of symlinks). Only remaining issue now is: everything is read-only even though the docker container console can delete/edit/create files.

I solved this by using rbind mount in /etc/fstab of my system OS, instead of symlinks! Works flawlessly. 

How come this works with FileRun on W10 but not with symlinks in Linux?

I have a  similar issue as SuAd, in Docker Compose I create volumes for each drive and map it to the container for FileRun.

- $USERDIR/docker/filerun/html:/var/www/html
- /mnt/pool/Users:/user-files:rw
- /mnt/pool/Collections:/local-files/Collections:rw

Via Portainer I open a console within the FileRun container to create symlinks from those mapped folders.

ln -s /local-files/Collections /user-files/Username/Shared/

But this does not work, because on the system filesystem, this structure does not exist.

The solution provided in the other topic is not OK, since it leads to an unwanted issue:

My system paths:



I want that last folder to appear in the home dir of 2 Filerun users.

If I simply add this to my docker-compose:

- /mnt/pool/Collections:/user-files/User1/Shared/Collections:rw

I can see and access the files in Collections folder, but in my OS, I now have /mnt/pool/Users/User1/Shared folder and its subfolder Collection, but that one is empty. --> that is very confusing for end users. 

2 things were necessary:

I had to change ownership of

sudo chown -R $USER:$USER ${USERDIR}/docker/filerun/esearch
sudo chmod 777 ${USERDIR}/docker/filerun/esearch

note I tried 644, 666. It only worked with 777. 

Yet the container would still fail.

If the host is running Debian or Ubuntu, according to the ElasticSearch documentation it says here you need to run the following command. The second command keeps it persistent after reboot of the host machine.

sudo sysctl -w vm.max_map_count=262144
sudo sh -c "echo 'vm.max_map_count=262144' >> /etc/sysctl.conf"

This solved the problem.
Perhaps this can be added to the documentation.

Is this still the recommended method to allow Dockerised FileRun access to your existing files?
I believe the above is not practical as it will do more I/O on your harddrive because Docker sees each of his 4 mounts as seperate filesystems.

Perhaps another method would be to mount a single path:


and create actual symlinks in /$USERDIR/docker/filerun/user-files to the actual folders you want access to.

So you will get

/$USERDIR/docker/filerun/user-files/Documents (which could be a symlink to /mnt/drive1/documents)

/$USERDIR/docker/filerun/user-files/Pictures ((which could be a symlink to /mnt/drive1/pictures)


Would that be the best method? Or should it be hardlinks instead? In order to maintain access to your files via other ways than FileRun?