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