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.
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.