Yes, I have it mapped as a letter drive on my server, which is what I pointed Docker at. My buddy was having the same issue with his server, for a different Docker container. After some digging, we both stumbled across a post on the docker forums that basically said networked drives don’t work with Docker, even when properly mapped. The container simply refuses to use them for volumes. They’ll look like they’re working, and the container will boot just fine. But nothing is actually read from/written to the NAS, and data isn’t persistent when the container is restarted. And that’s exactly what we were experiencing; The container would boot, but wasn’t usable because it couldn’t actually read/write anything.
Apparently for it to work properly, the container itself needs to contain nfs/smb libraries… And most don’t, because it’s considered bloat.
Have you tried properly mounting the network drive? Another option would be to just install audiobookshelf on the NAS.
Yes, I have it mapped as a letter drive on my server, which is what I pointed Docker at. My buddy was having the same issue with his server, for a different Docker container. After some digging, we both stumbled across a post on the docker forums that basically said networked drives don’t work with Docker, even when properly mapped. The container simply refuses to use them for volumes. They’ll look like they’re working, and the container will boot just fine. But nothing is actually read from/written to the NAS, and data isn’t persistent when the container is restarted. And that’s exactly what we were experiencing; The container would boot, but wasn’t usable because it couldn’t actually read/write anything.
Apparently for it to work properly, the container itself needs to contain nfs/smb libraries… And most don’t, because it’s considered bloat.