Jellyfin portainer stack completely reset after 10-hour server shutdown: why?

Hello!

I've recently deployed a Jellyfin portainer stack (exactly as shown in this video) and afterwards shut down the server by typing "shutdown" in the CLI. Now I am presented with the Jellyfin setup after the server started up again: why did this happen; do you have any ideas on how to prevent this?

Also, additional question: I'm trying to set up Plex and Jellyfin servers since one device that I am planning to stream this media to doesn't have a working Jellyfin program for it, is that possible? I've set up a Plex Server the other day and it worked perfectly, but now that I've mounted the same shared folders to also be accessible for Jellyfin and set up Jellyfin yesterday, I am getting a weird error when starting Plex! It says, "Please check that the file exists and the necessary drive is mounted." I know for a fact that the drive was mounted before mounting it also to Jellyfin, could it be that a shared folder can only be mounted once? Although it's ab SMB share and open to anyone! I do not understand.

TL; DR: How to stop Jellyfin from resetting itself after a restart (and how to set up Plex and Jellyfin simultaneously)?

Zitat von macom

Did you create a bind to /config?

Code

volumes:
      - /path/to/library:/config

https://hub.docker.com/r/linuxserver/jellyfin

Yes I did!

Zitat von KM0201

While that is certainly good advice to follow (with all of them, Plex, Emby, and Jellyfin).. I don't think that's his issue. I suspect when he rebooted, docker is starting before his storage drives are mounted... but given the fact he provided exactly zero information about his hardware/software setup, I can only speculate

I believe this must have been the reason. I edited the stack details and updated it, making it remount to all the volumes. Now it appears to be working, but I don't know if it'll continue to work once I reboot the server again.

Zitat von KM0201

Running both is simple, just run two different docker containers, pointed at different configs, but pointed at the same media library... just make sure there is no port issues between them.

They are pointed at different configs, yet I believe that for some reason whenever I restart both services cannot find the drive. It is an external drive, could it be that containers start up before the system recognizes the existance of external drives?

Zitat von johnvick

It's best to give Jellyfin read only access to your media shares (maybe Plex also but I don't use it). If you haven't then do so. It then stores its metadata etc in its own config files and database so less likely to interfere with another media playing system.

Well, Jellyfin creates awesome metadata that I believe Plex should use sometimes, and so far both services worked fine as seperate docker containers, yet when I restarted the server (the OMV not the container) they acted like none of the media existed.

Zitat von macom

You can write an override service file for docker. So that the start of docker is delayed by some second.

systemctl edit docker.service

paste

Code

[Service]
ExecStartPre=/bin/sleep 30
StartLimitInterval=300s

save and restart docker

Thank you SO much. I'll try to apply this and see if it will work!

Zitat von macom

You can write an override service file for docker. So that the start of docker is delayed by some second.

systemctl edit docker.service

paste

Code

[Service]
ExecStartPre=/bin/sleep 30
StartLimitInterval=300s

save and restart docker

It asks me for a filename on this, I thought I was editing an already existing file? Very confused.

Thanks, man! I edited it the way you described and will post the results until restarting the server. I now do also understand what I was doing!

Yeah, sorry! Wanted to do that yesterday, but also had lots of FTP uploads happening at the same time and I didn't want to disrupt that. But, good news:

When I turned on the server today and then looked at Jellyfin about a minute later (I know the script said 30 seconds, but that was for the entirety of Docker) everything worked! It did not act like a new setup and all the directories, including my config directory, seem to have mounted correctly!

Thank you so much everyone!