June 20, 201511 yr Previously, I have been running needo/nzbdrone:latest Sonar release, using an sshfs mount (mounted from unraid OS, not mounted inside the container) to a remote servver, mapped to the docker container using -v . The whole build line looks like: /usr/bin/docker run -d --name="Sonarr" --net="bridge" -e TZ="America/Los_Angeles" -p 9003:8989/tcp -v "/mnt/user/docker/config/sonarr/":"/config":rw -v "/mnt/user/TV-Shows/":"/tv":rw -v "/tmp/sshfs/":"/remoteSab":rw needo/nzbdrone This worked perfectly before RC and full release for unraid 6. Since upgrading, I can no longer read the sshfs file system. I have tried manually mounting the image with "--privileged" and (sperately) "--cap-add SYS_ADMIN --device /dev/fuse". I have also tried creating a sshfs mount within /tmp and /mnt/user/share, neither of which worked. Previous working Unraid Version: 6.0 beta 14 ( I think) Current version: 6.0.0 There is the possibility that one of the upgrades of the docker image also caused this to no longer be functional. All regular, non sshfs mounts still work, and have confirmed that file/folder permissions have not changed. Any assistance to troubleshooting this issue would be much appreciated. I am also open to different solutions, with the functionality desired is a remote-server secure folder mapping inside a docker container
Archived
This topic is now archived and is closed to further replies.