SOLVED: Updating Server on Ubuntu 24.10

[morrowindmemes]

I realized I didn't get the 10.10.4 update from the apt update. After that I went to /etc/apt/sources.list.d/jellyfin.sources:

Code:

Types: deb
URIs: https://repo.jellyfin.org/ubuntu
Suites: noble
Components: main
Architectures: amd64
Signed-By: /etc/apt/keyrings/jellyfin.gpg
Enabled:no

I deleted the line "Enabled:no" and after that I could successfully update to the latest version. After some reading I found that only LTS version would be supported form 10.9. So I wonder if what I did was wrong or is it not a good practice use noble build on oracular?

Also after updating. I noticed this on dashboard:
   

Normally on the web version it would say "10.10.4" not the last bit. Is this an artifact from the pronlem I mentioned above?

[TheDreadPirate]

You should be ok using noble builds on oracular. With the caveat that there is the possibility that a dependency that Jellyfin relies on could update and break Jellyfin. It is unlikely, but something to keep in mind.

Regarding the build number, try clearing your browser cache? If it is still there, it isn't anything to worry about.

Another option is to use Docker. You can use pretty much any distro that Docker supports.

[morrowindmemes]

You should be ok using noble builds on oracular.  With the caveat that there is the possibility that a dependency that Jellyfin relies on could update and break Jellyfin.  It is unlikely, but something to keep in mind.

Regarding the build number, try clearing your browser cache?  If it is still there, it isn't anything to worry about.

Another option is to use Docker.  You can use pretty much any distro that Docker supports.

Thanks for the info. I thought about switching to Docker but couldn't find out how to backup server settings and use them on docker.

[TheDreadPirate]

You wouldn't be able to drag and drop your current install's files into Docker, but it is possible to use your existing files with a little work.

You'd need to back up the following directories before trying, just to be safe.

/var/lib/jellyfin
/var/cache/jellyfin
/var/log/jellyfin
/etc/jellyfin

Our documentation contains the parameters you need to add to your docker config to make use of your existing files.

https://jellyfin.org/docs/general/admini...-to-docker

Essentially, a default Docker instance of Jellyfin writes everything to the virtual paths /config and /cache. Adding the environment variables specified in the documentation overrides the default Docker behavior.

[morrowindmemes]

Wow that was easy. I just backed up the dirs you mentioned, shutdown the server and then followed the docker-compose section of the tutorial and voila. Everything works exactly the same before. I thought cloudflare tunnel would give me some headache but nothing. Right now I only think about would be the linux install be more resource friendly compared to docker install cause the server is 2vcpu virtual machine on digitalocean.

[TheDreadPirate]

There is minimal memory overhead and little to no CPU overhead. Containers share the host OS's kernel vs a virtual machine, which has its own kernel.

Disk usage for the image and a bit more config complexity are the primary disadvantages. But the increased disk usage is due to containers bundling all their dependencies in the image. Which leads to the advantage that you don't have to worry about package conflicts between two apps installed on your system.

[morrowindmemes]

OK, thanks for your help again.