Ask Lemmy
A Fediverse community for open-ended, thought provoking questions
Rules: (interactive)
1) Be nice and; have fun
Doxxing, trolling, sealioning, racism, and toxicity are not welcomed in AskLemmy. Remember what your mother said: if you can't say something nice, don't say anything at all. In addition, the site-wide Lemmy.world terms of service also apply here. Please familiarize yourself with them
2) All posts must end with a '?'
This is sort of like Jeopardy. Please phrase all post titles in the form of a proper question ending with ?
3) No spam
Please do not flood the community with nonsense. Actual suspected spammers will be banned on site. No astroturfing.
4) NSFW is okay, within reason
Just remember to tag posts with either a content warning or a [NSFW] tag. Overtly sexual posts are not allowed, please direct them to either [email protected] or [email protected].
NSFW comments should be restricted to posts tagged [NSFW].
5) This is not a support community.
It is not a place for 'how do I?', type questions.
If you have any questions regarding the site itself or would like to report a community, please direct them to Lemmy.world Support or email [email protected]. For other questions check our partnered communities list, or use the search function.
6) No US Politics.
Please don't post about current US Politics. If you need to do this, try [email protected] or [email protected]
Reminder: The terms of service apply here too.
Partnered Communities:
Logo design credit goes to: tubbadu
view the rest of the comments
Mount the NAS share to whatever machine is hosting the Docker instance, then point your docker containers at that mount point.
I did. I have it mapped as a letter drive on my server. The server can access it just fine via the file browser. And the docker container still refuses to read from/write to it. The container boots up just fine on the surface, but the audiobooks volume appears empty when I check it (there are dozens in the folder) because the container refuses to actually read anything from the NAS. So I tried using the import option that Audiobookshelf has built in. It imported them just fine on the surface, but they all vanished as soon as the server was rebooted; Nothing was actually saved, because it is refusing to actually write to the NAS.
Testing with the local C drive, it worked flawlessly. No issues. I eventually stumbled across a forum post complaining about the same thing, and the responses were basically “yeah you can’t do that, Docker doesn’t support it unless the image itself has nfs/smb coded in. And most don’t, because it’s considered bloat and images are meant to be optimized.”
But since my server only has a 1TB drive for the OS, and everything else is done on the NAS, I can’t commit to storing all of my media on the server directly. So Audiobookshelf was dead in the water for me.
Sounds like a permissions issue, honestly. If the NFS share is mapped to a drive letter (Windows server I assume?), then Docker should see it in the filesystem like any other local drive. At least that's how I understand it... I've never used Docker on Windows.
Absolutely agreed on permission issue.
Sounds exactly like my issue.
I wasnt aware Linux accesses NFS shares with the authenticated user.
Linuxserver.io containers have a container user called 'abc' mapped via environment variables to the host.
Once I figured that out it was pretty easy.