Yesterday, 09:47 PM
It occurred to me that this might be a timing thing, and it does appear that Docker/Jellyfin was coming up before the system was mounting the shares.
For anyone finding this later:
- Since my system uses systemd, it apparently creates ".mount" entries for each of the entries in the fstab file. Using
- Now I could run
Now this apparently makes docker wait until that mount has finished mounting. I've rebooted a number of times, and it is now working without any issues.
I did go back and do some of the best practices that TheDreadPirate recommended, such as moving /cache and /config to a local folder (/jellyfin/cache and /jellyfin/config). I also really disliked the "/media/NAS/media" thing that I got from another post and moved it to "/mnt/nas/media", which felt like a better match.
Thanks!
For anyone finding this later:
- Since my system uses systemd, it apparently creates ".mount" entries for each of the entries in the fstab file. Using
systemctl list-units -t mount
let me find the name of this (mnt-media-nas.mount).- Now I could run
systemctl edit docker.service
to add:Code:
[Unit]
Requires=mnt-media-nas.mount
After=mnt-media-nas.mount
Now this apparently makes docker wait until that mount has finished mounting. I've rebooted a number of times, and it is now working without any issues.
I did go back and do some of the best practices that TheDreadPirate recommended, such as moving /cache and /config to a local folder (/jellyfin/cache and /jellyfin/config). I also really disliked the "/media/NAS/media" thing that I got from another post and moved it to "/mnt/nas/media", which felt like a better match.
Thanks!