There are two more Iād reccomend as its what my family and friends have been using and have ran into literally, zero issues.
Linux mint (specifically cinnamon edition) is very stable, and customizable if youāre into that sorta thing, you can install custom kernels and get greatly improved performance out of gaming if thats your thing. Itās built off of Ubuntu (but just better) so thereās great support for it, especially with devices such as printers.
Fedora Kinoite is a solid, also well supported, immutable distribution which will either make your life easier, or more difficult.
Immutable means you canāt change anything in your root directory, so basically your āC: Driveā. You still have a regular file system and can install all your apps, but the operating system stays the same as everyone elseās and is something that by design, never breaks and ājust worksā, and is what I personally use.
Pop_OS is definitely another option if you have ānewerā hardware and Linux Mint doesnāt work for you and you donāt like the immutability of Fedora Kinoite (you can always try regular Fedora KDE). But Iād personally reccomend just the first two. But Pop is also built off of Ubuntu, so you still get that great hardware support.
But please, avoid stock Ubuntu. Ubuntu has far gone away from being a beginner, ājust worksā distro.
Hope this helped! Please reply or message me if you have any issues or are confused, or you can always ask for some more help within this community as well!
Iām using Rocky on my main server at the moment, I was/am used to Debian based operating systems beforehand but wanted to learn red hat without dealing with Oracle directly.
It was definitely a step curve getting to understanding the os but Iām quite happy with the stability of Rocky and it does everything I need and more. I think the real question is which would you get more enjoyment out of as far as learning and personally I donāt think the learning curve is as steep with Debian.
The best thing I can advise is just back up your data regularly and if youāre not vibing or something breaks donāt be afraid to change to something different, though as an arch user Iām sure youāre used to things breaking.
Debian stable is a very solid choice for a server OS.
It depends on how youāre going to host your services though. Are you going to use containers (what kind), VMs, a mix of the two, install directly on the host system (and if so where do you plan to source the packages)?
Iāve kept my Debian system very basic, installed latest Docker from the official apt repo, and Iāve installed almost every service in a docker container. Only things installed directly on host are docker, ssh, nfs and avahi.
Make sure you use a docker image that tracks the stable version of Jellyfin. The official image jellyfin/jellyfin tracks unstable. Not all plugins work with unstable and switching to stable later is difficult. This trips lots of people and locks them into unstable because by the time they figure it out theyāve customized their collection a lot.
The linuxserver/jellyfin image carries stable versions but you have to go into the āTagsā tab and filter for 10. to find them (10.8.13 pushed 16 days ago is the latest right now).
To use that version you say āimage: linuxserver/jellyfin:10.8.13ā in your docker compose instead of ālinuxserver/jellyfin:latestā.
This approach has the added benefit of letting you control when you want to update Jellyfin, as opposed to :latest which will get updated whenever the container (re)starts if thereās a newer image available.
While upgrading your images constantly sounds good in theory, eventually you will see that sometimes the new versions will break (especially if theyāre tracking unstable versions). When that happens you will want to go back to a known good version.
What I do is go look for tags every once in a while and if thereās a newer version I comment-out the previous āimage:ā line and add one with the new version, then destroy and recreate the container (the data will survive because you configure it to live on a mounted volume, not inside the container), then recreate with the new version. If thereās any problem I can destroy it, switch back to the old version, and raise it again.
Oh that explains the 2 linuxserver and official jellyfin then. It was always kinda strange to me.
Luckily my uni hosted a docker course and binge watched a beginner Linkedin Learning too about it, but Iām really grateful for your in-depth guide. Guys like you really make Lemmy the old Reddit you used to have and cherish in your hearts. :3
The official image jellyfin/jellyfin tracks unstable
Why did they make that choice? I am on this version right now, didnāt know it was unstable. I found it very difficult to have information regarding the docker images in general, itās a pity we donāt have a few lines explaining what the content is.
Itās more like ālatestā tracks unstable, because unstable evolves much faster and it puts out versions more often. Unfortunately thereās a practice going around that makes people just the :latest tag for everything and they donāt always stop to consider the implications (which may be different for each project).
The official image jellyfin/jellyfin tracks unstable
Huh? That doesnāt appear to be the case. jellyfin/jellyfin:latest, which is what they tell you to use in the installation instructions. gives me 10.8.13 which appears to be the latest stable release.
There are newer and unstable versions available in dockerhub as well, but latest doesnāt give you those. After all latest is just a tag with no special meaning of itself, it doesnāt necessarly give you the most recent build.
linux
Hot
This magazine is from a federated server and may be incomplete. Browse more on the original instance.