Possible bug?

Posted by waffle38930

Hello, I thought I'd post about something that I noticed yesterday after updating. So my files are hosted on my NAS which I set up to mount to Jellyfin via the volumes parameter in the compose docker file. After my update, my Jellyfin library stopped working. After doing a little digging, the only conclusion I could come to was the update and reset my compose.yaml file? Is this possible and if so, could this be omitted from changes with future updates? Cheers

4 replies

tomspark wrote:

Yeah, sparkbox update replaces the bundled module/docker-compose.yml files — that's how fixes ship, so any custom edits there get wiped. For Jellyfin media specifically the supported path is the MEDIAROOT env var in /opt/sparkbox/.env. Set it to your NAS mount path, e.g.: MEDIAROOT=/mnt/nas/media Then sudo sparkbox restart media. Jellyfin sees everything under that root as /data inside the container, no compose edits needed, and updates won't wipe it. If you needed more than one mount or named subpaths, paste what you had in the compose and I'll see if the bundle can absorb it or if it's worth adding a user-override-compose hook for v1.7.

waffle38930 wrote:

Ahh thats awesome, sorry yeah, I added the mount path to the .env file. That makes way more sense! Thanks :D

tomspark wrote:

Nice. Yell back if anything else breaks after an update.

tomspark wrote:

Nice, glad that fixed it. The MEDIAROOT env var approach keeps your config safe across updates, so you're all set now.