I have a Jellyfin container that uses a network mount to access my video files. The mount is set up with the command (--mount type=bind,source=/mnt/media,target=/media). Everything works perfectly when I start the container manually, but it refuses to start automatically on boot. I suspect the issue is that the network mount isn't ready when Docker tries to start Jellyfin. I've tried removing the mount, and then the container starts without any issues, but of course, that means I can't access my media. Is there a way to get around this, like having Docker wait for the network share to be available before starting Jellyfin?
1 Answer
Check the start order of processes on your system. Since I use systemd, I can ensure that things like networking and mounts start before my Jellyfin instance. You could also create a wrapper script for your container that verifies the mount is available before launching it. Let me know your setup, and we can figure out what's going wrong!
I use fstab for my media mounts too, and while it works perfectly, I think it fails to mount before Docker starts Jellyfin. I’m running Debian 13 on Proxmox. How do I set up systemd to manage the startup sequence?