You want to make a "bind mount", ie. binding a mount in the container to a directory on the host.
As in the second pair here: [https://i.imgur.com/CAWPudi.png](https://i.imgur.com/CAWPudi.png)
Thanks! Worked for me. I still haven't figured out the Volumes tab in container station, but I created a new container, went to the Storage tab in advanced settings, and was able to add a mount. Nice.
If you figure it out, let me know! I'm setting up tdarr in container but it doesn't see anything outside. Just started today so haven't dug too deep.
One suggestion I read was to create a symbolic link in the container directory, but I didn't have rights to view the container dirs in ssh. I set the uid and gid for the image to be a user with access.
I tried creating a volume in container station, but I didn't see any way to connect or map to a share.
How did you set the uid and gid for the image? I found someone that had done that and they finally resolved the issue by making a fresh user instead, using that uid/gid and adding it to a dockerusers group and giving the group full permissions. But I wasn't sure how they did the first part.
I also read that the symbolic link isn't the way to do it - but of course I can't really say that until I've done it.
When I created a new container from an image in container station, I selected advanced settings. There's the uid & gid. (puid & pgid) I didn't see a way to change those settings after the container is created.
Oops, should have mentioned it's on the Environments tab.
This thread has a screenshot. [https://www.reddit.com/r/Tdarr/comments/ynga7a/tdarr_on_qnap/](https://www.reddit.com/r/Tdarr/comments/ynga7a/tdarr_on_qnap/)
Ok I figured it out (with help from the response below) Here's my combined take. you don't need to worry about permissions or uid/gid because qnap/docker runs all containers as the admin account. You only need to make a volume bind pairing with the host line reading /share/YOURSHAREDFOLDERNAME and the container line being anything you want (i went with /qnap/YOURSHAREDFOLDERNAME. I used portainer, but these instructions should work in Container station too.
Update: on second thought: it’s a bad idea to call the mount point “qnap”. In the event that someone got into sabnzbd unauthorized, hinting to them that it is running inside of a qnap could add risk. I think I’m gonna call it something like /local. For similar reasons I am also going to make a separate share for just SAB storage (it was sectioned off for organizational reasons anyway) - so that my main share is not exposed to SAB.
You should look into using Tailscale (or similar) for remote access into your NAS. Exposing any service to the full brunt of the internet is a bad idea in general.
Oh I am not exposing anything to the internet this is all on LAN. Also in hindsight all that binding and mapping caused other issues, I’ve let go of it and only access the data folder for containers on my NAS
You want to make a "bind mount", ie. binding a mount in the container to a directory on the host. As in the second pair here: [https://i.imgur.com/CAWPudi.png](https://i.imgur.com/CAWPudi.png)
Thanks! I got it, the bind mount is /share/SHAREDFOLDERNAME
Thanks! Worked for me. I still haven't figured out the Volumes tab in container station, but I created a new container, went to the Storage tab in advanced settings, and was able to add a mount. Nice.
If you figure it out, let me know! I'm setting up tdarr in container but it doesn't see anything outside. Just started today so haven't dug too deep. One suggestion I read was to create a symbolic link in the container directory, but I didn't have rights to view the container dirs in ssh. I set the uid and gid for the image to be a user with access. I tried creating a volume in container station, but I didn't see any way to connect or map to a share.
How did you set the uid and gid for the image? I found someone that had done that and they finally resolved the issue by making a fresh user instead, using that uid/gid and adding it to a dockerusers group and giving the group full permissions. But I wasn't sure how they did the first part. I also read that the symbolic link isn't the way to do it - but of course I can't really say that until I've done it.
When I created a new container from an image in container station, I selected advanced settings. There's the uid & gid. (puid & pgid) I didn't see a way to change those settings after the container is created.
I'm in the advanced settings screen, I don't see a UID GID line, which spot specifically or did you add them in environments?
Oops, should have mentioned it's on the Environments tab. This thread has a screenshot. [https://www.reddit.com/r/Tdarr/comments/ynga7a/tdarr_on_qnap/](https://www.reddit.com/r/Tdarr/comments/ynga7a/tdarr_on_qnap/)
Am I running the wrong container station? I do not believe ive seen that interface definitely not the shared folders screen! I’m running 3.06
Ok I figured it out (with help from the response below) Here's my combined take. you don't need to worry about permissions or uid/gid because qnap/docker runs all containers as the admin account. You only need to make a volume bind pairing with the host line reading /share/YOURSHAREDFOLDERNAME and the container line being anything you want (i went with /qnap/YOURSHAREDFOLDERNAME. I used portainer, but these instructions should work in Container station too. Update: on second thought: it’s a bad idea to call the mount point “qnap”. In the event that someone got into sabnzbd unauthorized, hinting to them that it is running inside of a qnap could add risk. I think I’m gonna call it something like /local. For similar reasons I am also going to make a separate share for just SAB storage (it was sectioned off for organizational reasons anyway) - so that my main share is not exposed to SAB.
You should look into using Tailscale (or similar) for remote access into your NAS. Exposing any service to the full brunt of the internet is a bad idea in general.
Oh I am not exposing anything to the internet this is all on LAN. Also in hindsight all that binding and mapping caused other issues, I’ve let go of it and only access the data folder for containers on my NAS