We are doing a pilot with FileRun to determine if we like it more than Nextcloud for our needs. We are looking at buying the enterprise edition, but the pilot needs to be successful before we can commit.
We are running the docker-based version of FileRun on a Kubernetes cluster, with volumes backed by SMB, and we've found strange behavior with the files that FileRun serves. Essentially, FileRun is not able to serve files intact from the SMB volume. The issue matches almost exactly with the behavior described here:
However, we have found that even modifying/extending the Docker image to configure Apache to use neither Sendfile nor MMAP has no effect on the issue. I have even tried removing
to disable XSendFile but that similarly has had no effect on the issue.
If we use NFS-based volumes or emptyDir volumes, the issue is not present, so this appears to be an issue with the way that FileRun/Apache interact with SMB. NFS isn't an option for production usage because it doesn't support transport-level authentication (i.e. we can't prevent other applications/pods/containers in the cluster from connecting to the NFS share and being able to read files that they should not be able to read).
Customer support service by UserEcho