I’ll add my vote as it’s not been mentioned: DietPi - based on Debian (since the majority are recommending that) and has a really easy “one click” menu system to install apps (of which include Jellyfin, Plex). And a built in updater to keep everything up to date. And it’ll install on pretty much anything (SBCs, new PCs, old PCs, VMs).
No need to use docker, it installs everything directly, though it does support it if you want to go down that route.
Or, DietPi with CasaOS which is a web interface and app store for docker installations.
The biggest advantage for docker in the “home lab” environment is to be able to try out an app, but if you decide you don’t like it, removal is simply deleting the container and the data folder. That’s it. No trace left.
Sadly you can’t say that for installed apps.
But I agree, if it ain’t broke, don’t fix it. Seems DietPi will be right up your street and look after things exactly how you want, simply 😁
Originally it was for the Pi, but can also be installed on x64 PC systems, either UEFI or BIOS, so basically runs on anything. It does run great on a Pi, it’s biggest advantage being that it logs to RAM, which massively saves on SD card wear. It’s also the only current distro which works reliably on the original Pi 1 nowadays (if you still have those hanging around!)
And I get that everyone saying “Docker!” is a bit boring, but there is a reason for it - containerising everything does make it a lot easier to manage and migrate everything to another system or revert back a single component to a different version. And you just backup a config file and your data folder for each container and you can recreate your system so easily. If you install directly, you have to worry about databases, file paths, permissions… but as you said, there’s nothing wrong with just installing stuff. Especially if it’s only a few programs.
I run 26 docker containers. Installing all those on a system would be a mess…
To counter my own “easy to migrate” argument, DietPi includes a backup utility called ‘dietpi-backup’ (genius naming convention, I know!) which you can use to backup your whole system to another drive. And of course restore your whole setup on a clean install.
Also very useful for rollbacks if needed. I have a 2.5in 5400rpm 1TB drive attached to my DietPi server which is just for backups - it backs up every night at 2am and it’s incremental too. I have 5 days of backups and it’s one command and a couple of ‘Enters’ to get it rolling back to an earlier config - really easy and useful when a recent kernel update broke my ethernet adapter (Debian’s fault - not DietPi!).
this specific machine is not meant for change. Ever.
Debian
Bonus round: anyone who’s ever transferred Plex servers from win to Linux (insert flavor), is it actually possible to keep my collections and playlists and stuff?
Yes, it’s relatively simple, especially with Docker. Back up the Plex folder from your windows machine. Once your new OS is set up, put the folder where you wanna store it and point Docker to that folder in the compose.yaml.
I would recommend using Docker first on the windows machine as a step in the transition. I did exactly this when I was transitioning to debian from windows. It made the official switch insanely easy because all I had to do was set up the Docker filesystem to what it already knew and it started up without any issues.
My lessons learned:
Keep the database on an SSD. I put mine on a HDD and it corrupted.
Keep the database on an SSD. I put mine on a HDD and it corrupted.
That seems very odd to me, and a very serious bug, no? 🤨 I feel like the storage medium shouldn’t matter as long as it can keep up with data throughput (or eventually keep up, with some help with buffering via the kernel or some other mechanism).
When you say database, do you mean the OS and the server install?
Yes, that’s what I meant. I switched my server install to a HDD because it was running on a 256 GB SSD which was running out of room.
I’m sure docker is easier if you know it… that’s like the point, afaik, but while basic use might be easy, it’s… never ever that easy for me, something always goes wrong, which is why I haven’t bothered yet. I know I should, I know it’ll make things easier (hypothetically), but it feels like a huge undertaking for someone with no skills. I’ve been looking for a super noob friendly instruction guide, and have not found one that I can work with, tbh, without a bunch of other know-how that I don’t have. (If you know of any I’d be eternally grateful!!!)
I can give you some tips for now and then I’ll give you some more in-depth instructions when I’m at my computer again.
For now:
Install Docker to your computer. I’m not sure how windows Docker handles it but I recommend using Docker compose. I’m not sure of the technical differences between Docker and Docker compose, but I found Docker compose to be much easier to use because it’s saved as a YAML file (text file). If you need to make changes, just edit the file.
Once you have that set up, get a Plex server running. You’ll probably have to change the ports in the Docker one to avoid conflict with your current one.
I recommend LinuxServer.io for a lot of things, including Plex. There’s some dissent over use of Linux Server’s apps due to permission and root things, but they are also super simple to use and you can start with the basics here.
Scroll down a bit to find the docker-compose section. To start a sample plex server, make the following changes:
Remove network_mode: host
In line with environment and volumes, add this: ports - 324001:32400
This will route 32400 of the docker container to 32401 of the host network, allowing you to have both servers running at the same time without a port conflict.
Edit the volumes as needed. Always remember, it goes: host: container for everything. You can change it however you need. /config should preferably be on an SSD, as I said. The rest can be created as needed. For mine, I have both movies and TV shows stored under a folder called /media/. My plex docker script mounts /media/ and in plex I can search through the subdirectories to find the TV and Movies section.
Your second (temporary) plex server should be set up properly once you start the container
I’ll tell you how to data over to the Docker container later.
As a person who has been managing Linux servers for about a decade now, trust me that a few hours or days of learning docker now will save you weeks if not months in the future. Docker makes managing servers and dealing with updates trivial and predictable. Setting everything up in docker compose makes it easy to recover if something fails, it’s it’s self documenting because you can quickly see exactly how your applications are configured and running.
Is there a reason you’re not considering running this in a VM?
I could see a case where you go for a native install on a virtual machine, attach a virtual disk to isolate your library from the rest of the filesystem, and then move that around (or just straight up mount that directory in the container) as needed.
That way you can back up your library separately from your JF server implementation and go hog wild.
But this post didn’t suggest Docker, it suggested a VM. This would be a totally sensible thing to do as you can just recreate it if you mess it up. Virtualbox works fine on Windows and Linux. Install it and spin up a distro.
Mate, the suggestions you have been given for VMs and docker are to help you recover easily should you mess up. If you are going to moan about that…maybe just install bare metal and get on with it yourself?
Without docker you still just copy your files from Windows to Linux, though you have to find the right directories for that. Jellyfin can be installed directly on Debian. Just add their repo and go
Another vote for Debian, and I’ll suggest you go ahead and install Jellyfin directly rather than messing with Docker. https://jellyfin.org/downloads/server
I’d been running JF under Docker on my NAS, but when I moved to a new server I decided to just install it directly and it hasn’t been any problem at all. You’ll get a notification when it needs to be updated and it’s just a few clicks to do so. You won’t have to fight with Docker to get hardware acceleration working - which isn’t to say it won’t be a PITA, but it’s one less layer of complication.
Debian is always the answer for a stable, easy to set up server OS.
You don’t need to use Docker if you don’t want to, you can install Plex/Jellyfin using their normal apt repos instead.
Bonus round: anyone who’s ever transferred Plex servers from win to Linux (insert flavor), is it actually possible to keep my collections and playlists and stuff?
Yes, transfer your plex database and that will come with it.
It sounds like you don’t necessarily like the idea of using a container (I tend to use podman, but most guides are for docker, so that’d probably be easier for you). From my experience, containerising things actually makes things a lot easier, especially in the long run, and getting started is a lot easier than it seems. You can probably find a ready-made guide to set up a plex or jellyfin container on Debian.
If you use docker, it doesnt matter the distro. And to use docker, you dont really need to understand how/why it works. As long as you can take an example compose file and spin it up (docker compose up) it’ll be less complicated in the long run than managing plex on the host machine (or most software for that matter, which is why containerization is so popular.)
I really think the learning curve will be less than you think. Please consider at least reading the installation instructions. Here’s the page for linuxserver.io’s maintained plex docker container. I’ve linked to the usage section, where you can copy the compose file to deploy it. https://github.com/linuxserver/docker-plex?tab=readme-ov-file#usage
If you really don’t want Debian, the next answer is Rocky or Alma.
really good file management options; bulk rename with rules is a must even if it’s an additional program
This has nothing to do with the distro. Powerful rename tools are available everywhere. Personally, I just let Radarr etc. handle the importing and renaming of files and I never touch them (well, hardly ever).
Docker is pretty easy to use, and is easy to play with either on your own system (linux or windows) or in VM guest system. The learning curve isn’t that high and Jellyfin for example has a clear set up guide for docker on their wiki.
But radarr, sonarr etc can be installed directly within linux without docker. The Servarr wiki (that these projects use officially to share information as they’re so similar) has lots of straight forward guides for set up on Linux, Windows, Mac etc as well as Docker.
I have a Linux guest VM set up with a Radarr, Sonarr etc set up, VPN and torrent set up. It was easy to do and means its network activity is all securely contained away from my host system. The tools let me set naming rules and file preferences. The library is a shared n folder in my host system, and that is included in my Jellyfin library. So all I have to do is subscribe to something i am interested in and it will just appear in my library once downloaded. The servarr tools are extremely convenient and worth looking at if you’re adding to that 30tb library over time.
everything I’ve seen for radarr, sonarr, overseerr, etc. require docker
Back when I was using Sonarr a couple years ago before that really good free tracker died, I wasn’t using docker at all. Just a systemd unit for the server and one for the web interface I believe, or maybe just the one for both. I’m on Arch.
Ubuntu server, it’s a bit more modern than Debian and has a massive install base which means someone has had your problem and fixed it before and documented it.
I use Fedora Server with Podman (instead of Docker). I am not a noob either, but cockpit provides a really useful GUI for managing the whole operating system.
Syntax-wise, it’s meant to be identical. I got on board when they were the only ones that enabled rootless (without admin privileges) mode. That’s no longer the case since rootless docker has been out for a while.
I’m personally a fan of the red hat docs and how-to’s on podman over the mixed bag of tech bro medium articles I associate with docker.
At the end of the day this is a bit of a Pokemon starter question. If your top priority is to get a reasonably common and straightforward job done just pick one and see where it takes you! :)
Fella, you have a huge knowledge deficit for what you’re trying to do here…
Docker does make running services easier and isn’t overkill for what you’re doing. But it’s not necessary and it’s fine if you don’t want to use it.
Debian is fine as well.
You need to get some experience before you continue self-hosting. Start firing up some vms or something. If that seems like “too much work” then perhaps this hobby isn’t for you. Running servers isn’t like grabbing an app from the app store. You’re going to need to invest some time here.
:) you don’t have to use containers, but they do simplify the install.
I don’t use containers.
There’s also no Setup.exe to download run where you just Next, Next, Finish.
So, instead, I have to install separate packages, configure them, deal with conflicting requirements, etc…
Did I have to learn Docker? No. Did I have to learn something else? Yes.
As someone else mentioned, spending some time learning what / how / why you’re doing will help massively later on.
Probably why you’re getting Docker answers, they’re auto-suggesting it to start you off with something simpler…
Ignore the noise and use Ubuntu LTS. Subscribe for the free Ubuntu Pro service. This is something you do not get on Debian. Enjoy boring, trouble-free operation.
If you’re hell bent on not using Ubuntu, use Debian. Enjoy boring, trouble-free operation.
In either case, use Docker. I don’t know what the version of Docker is in Debian but in Ubuntu 22.04 LTS, it’s recent enough so you don’t have to f around with third party repos.
Take a distro with a package manager you are familiar with. Debian should do it.
And try out docker it’s really easy to learn and straight forward.
Jellyfin has a well documented docker compose.yml which is just a textfile that points out the facts like used versions, environment and volume paths.
I did a transition from my docker compose tools to a new system in under an hour yesterday. All I had to do was backup the volumes or data paths. Firing up the containers looks like a new install but it’s just downloading the container and everything runs like before without losing any config.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !selfhosted@lemmy.world
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don’t control.
Rules:
Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it’s not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.
Resources:
selfh.st Newsletter and index of selfhosted software and apps
I’ll add my vote as it’s not been mentioned: DietPi - based on Debian (since the majority are recommending that) and has a really easy “one click” menu system to install apps (of which include Jellyfin, Plex). And a built in updater to keep everything up to date. And it’ll install on pretty much anything (SBCs, new PCs, old PCs, VMs).
No need to use docker, it installs everything directly, though it does support it if you want to go down that route.
Or, DietPi with CasaOS which is a web interface and app store for docker installations.
Lastly, Plex have their own guide on what you need to copy to move your Plex data from one system to another: https://support.plex.tv/articles/201370363-move-an-install-to-another-system/
deleted by creator
What made you feel that way? (I’m not too familiar with docker much tbh and I’m thinking of hosting on a Pi just like you.)
deleted by creator
The biggest advantage for docker in the “home lab” environment is to be able to try out an app, but if you decide you don’t like it, removal is simply deleting the container and the data folder. That’s it. No trace left.
Sadly you can’t say that for installed apps.
But I agree, if it ain’t broke, don’t fix it. Seems DietPi will be right up your street and look after things exactly how you want, simply 😁
‘apt purge’ does a fine job of cleaning up.
Docker has other advantages though.
Originally it was for the Pi, but can also be installed on x64 PC systems, either UEFI or BIOS, so basically runs on anything. It does run great on a Pi, it’s biggest advantage being that it logs to RAM, which massively saves on SD card wear. It’s also the only current distro which works reliably on the original Pi 1 nowadays (if you still have those hanging around!)
And I get that everyone saying “Docker!” is a bit boring, but there is a reason for it - containerising everything does make it a lot easier to manage and migrate everything to another system or revert back a single component to a different version. And you just backup a config file and your data folder for each container and you can recreate your system so easily. If you install directly, you have to worry about databases, file paths, permissions… but as you said, there’s nothing wrong with just installing stuff. Especially if it’s only a few programs.
I run 26 docker containers. Installing all those on a system would be a mess…
deleted by creator
To counter my own “easy to migrate” argument, DietPi includes a backup utility called ‘dietpi-backup’ (genius naming convention, I know!) which you can use to backup your whole system to another drive. And of course restore your whole setup on a clean install.
Also very useful for rollbacks if needed. I have a 2.5in 5400rpm 1TB drive attached to my DietPi server which is just for backups - it backs up every night at 2am and it’s incremental too. I have 5 days of backups and it’s one command and a couple of ‘Enters’ to get it rolling back to an earlier config - really easy and useful when a recent kernel update broke my ethernet adapter (Debian’s fault - not DietPi!).
Debian
Debian
Debian
Yes, it’s relatively simple, especially with Docker. Back up the Plex folder from your windows machine. Once your new OS is set up, put the folder where you wanna store it and point Docker to that folder in the compose.yaml.
Does the docker container have gpu access for transcoding?
It is possible to pass transcoding - I’ll share my compose file when I’m at my computer
Yes, if you pass the gpu into the container
Man, if the “Download more RAM!” scammers of old could see us now.
deleted by creator
I would recommend using Docker first on the windows machine as a step in the transition. I did exactly this when I was transitioning to debian from windows. It made the official switch insanely easy because all I had to do was set up the Docker filesystem to what it already knew and it started up without any issues.
My lessons learned:
Keep the database on an SSD. I put mine on a HDD and it corrupted.
That seems very odd to me, and a very serious bug, no? 🤨 I feel like the storage medium shouldn’t matter as long as it can keep up with data throughput (or eventually keep up, with some help with buffering via the kernel or some other mechanism).
¯\_(ツ)_/¯
I put it on a larger HDD because my SSD was running out of space and it corrupted about a week later.
Nothing to do with it being an hdd.
Millions of database have run on hdds for decades just fine. They didn’t know what they’re talking about.
deleted by creator
Yes, that’s what I meant. I switched my server install to a HDD because it was running on a 256 GB SSD which was running out of room.
I can give you some tips for now and then I’ll give you some more in-depth instructions when I’m at my computer again.
For now:
Install Docker to your computer. I’m not sure how windows Docker handles it but I recommend using Docker compose. I’m not sure of the technical differences between Docker and Docker compose, but I found Docker compose to be much easier to use because it’s saved as a YAML file (text file). If you need to make changes, just edit the file.
Once you have that set up, get a Plex server running. You’ll probably have to change the ports in the Docker one to avoid conflict with your current one.
I recommend LinuxServer.io for a lot of things, including Plex. There’s some dissent over use of Linux Server’s apps due to permission and root things, but they are also super simple to use and you can start with the basics here.
https://docs.linuxserver.io/images/docker-plex/
Scroll down a bit to find the docker-compose section. To start a sample plex server, make the following changes:
Remove
network_mode: hostIn line with environment and volumes, add this:
ports - 324001:32400This will route 32400 of the docker container to 32401 of the host network, allowing you to have both servers running at the same time without a port conflict.
Edit the volumes as needed. Always remember, it goes: host: container for everything. You can change it however you need. /config should preferably be on an SSD, as I said. The rest can be created as needed. For mine, I have both movies and TV shows stored under a folder called /media/. My plex docker script mounts /media/ and in plex I can search through the subdirectories to find the TV and Movies section.
Your second (temporary) plex server should be set up properly once you start the container
I’ll tell you how to data over to the Docker container later.
As a person who has been managing Linux servers for about a decade now, trust me that a few hours or days of learning docker now will save you weeks if not months in the future. Docker makes managing servers and dealing with updates trivial and predictable. Setting everything up in docker compose makes it easy to recover if something fails, it’s it’s self documenting because you can quickly see exactly how your applications are configured and running.
Is there a reason you’re not considering running this in a VM?
I could see a case where you go for a native install on a virtual machine, attach a virtual disk to isolate your library from the rest of the filesystem, and then move that around (or just straight up mount that directory in the container) as needed.
That way you can back up your library separately from your JF server implementation and go hog wild.
deleted by creator
But this post didn’t suggest Docker, it suggested a VM. This would be a totally sensible thing to do as you can just recreate it if you mess it up. Virtualbox works fine on Windows and Linux. Install it and spin up a distro.
Mate, the suggestions you have been given for VMs and docker are to help you recover easily should you mess up. If you are going to moan about that…maybe just install bare metal and get on with it yourself?
Without docker you still just copy your files from Windows to Linux, though you have to find the right directories for that. Jellyfin can be installed directly on Debian. Just add their repo and go
Another vote for Debian, and I’ll suggest you go ahead and install Jellyfin directly rather than messing with Docker.
https://jellyfin.org/downloads/server
I’d been running JF under Docker on my NAS, but when I moved to a new server I decided to just install it directly and it hasn’t been any problem at all. You’ll get a notification when it needs to be updated and it’s just a few clicks to do so. You won’t have to fight with Docker to get hardware acceleration working - which isn’t to say it won’t be a PITA, but it’s one less layer of complication.
Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I’ve seen in this thread:
[Thread #849 for this sub, first seen 4th Jul 2024, 02:55] [FAQ] [Full list] [Contact] [Source code]
Debian is always the answer for a stable, easy to set up server OS.
You don’t need to use Docker if you don’t want to, you can install Plex/Jellyfin using their normal apt repos instead.
Yes, transfer your plex database and that will come with it.
It sounds like you don’t necessarily like the idea of using a container (I tend to use podman, but most guides are for docker, so that’d probably be easier for you). From my experience, containerising things actually makes things a lot easier, especially in the long run, and getting started is a lot easier than it seems. You can probably find a ready-made guide to set up a plex or jellyfin container on Debian.
I use Alpine Linux for all my dockers, small and fast.
If you use docker, it doesnt matter the distro. And to use docker, you dont really need to understand how/why it works. As long as you can take an example compose file and spin it up (docker compose up) it’ll be less complicated in the long run than managing plex on the host machine (or most software for that matter, which is why containerization is so popular.)
deleted by creator
I really think the learning curve will be less than you think. Please consider at least reading the installation instructions. Here’s the page for linuxserver.io’s maintained plex docker container. I’ve linked to the usage section, where you can copy the compose file to deploy it. https://github.com/linuxserver/docker-plex?tab=readme-ov-file#usage
Standard answer: Debian.
If you really don’t want Debian, the next answer is Rocky or Alma.
This has nothing to do with the distro. Powerful rename tools are available everywhere. Personally, I just let Radarr etc. handle the importing and renaming of files and I never touch them (well, hardly ever).
deleted by creator
Docker is pretty easy to use, and is easy to play with either on your own system (linux or windows) or in VM guest system. The learning curve isn’t that high and Jellyfin for example has a clear set up guide for docker on their wiki.
But radarr, sonarr etc can be installed directly within linux without docker. The Servarr wiki (that these projects use officially to share information as they’re so similar) has lots of straight forward guides for set up on Linux, Windows, Mac etc as well as Docker.
I have a Linux guest VM set up with a Radarr, Sonarr etc set up, VPN and torrent set up. It was easy to do and means its network activity is all securely contained away from my host system. The tools let me set naming rules and file preferences. The library is a shared n folder in my host system, and that is included in my Jellyfin library. So all I have to do is subscribe to something i am interested in and it will just appear in my library once downloaded. The servarr tools are extremely convenient and worth looking at if you’re adding to that 30tb library over time.
deleted by creator
deleted by creator
Back when I was using Sonarr a couple years ago before that really good free tracker died, I wasn’t using docker at all. Just a systemd unit for the server and one for the web interface I believe, or maybe just the one for both. I’m on Arch.
I hope that helps.
deleted by creator
Debian
Ubuntu server, it’s a bit more modern than Debian and has a massive install base which means someone has had your problem and fixed it before and documented it.
deleted by creator
I use Fedora Server with Podman (instead of Docker). I am not a noob either, but cockpit provides a really useful GUI for managing the whole operating system.
deleted by creator
Syntax-wise, it’s meant to be identical. I got on board when they were the only ones that enabled rootless (without admin privileges) mode. That’s no longer the case since rootless docker has been out for a while.
I’m personally a fan of the red hat docs and how-to’s on podman over the mixed bag of tech bro medium articles I associate with docker.
At the end of the day this is a bit of a Pokemon starter question. If your top priority is to get a reasonably common and straightforward job done just pick one and see where it takes you! :)
deleted by creator
deleted by creator
deleted by creator
deleted by creator
deleted by creator
Fella, you have a huge knowledge deficit for what you’re trying to do here…
Docker does make running services easier and isn’t overkill for what you’re doing. But it’s not necessary and it’s fine if you don’t want to use it.
Debian is fine as well.
You need to get some experience before you continue self-hosting. Start firing up some vms or something. If that seems like “too much work” then perhaps this hobby isn’t for you. Running servers isn’t like grabbing an app from the app store. You’re going to need to invest some time here.
:) you don’t have to use containers, but they do simplify the install.
I don’t use containers.
There’s also no Setup.exe to download run where you just Next, Next, Finish.
So, instead, I have to install separate packages, configure them, deal with conflicting requirements, etc…
Did I have to learn Docker? No. Did I have to learn something else? Yes.
As someone else mentioned, spending some time learning what / how / why you’re doing will help massively later on. Probably why you’re getting Docker answers, they’re auto-suggesting it to start you off with something simpler…
Ignore the noise and use Ubuntu LTS. Subscribe for the free Ubuntu Pro service. This is something you do not get on Debian. Enjoy boring, trouble-free operation.
If you’re hell bent on not using Ubuntu, use Debian. Enjoy boring, trouble-free operation.
In either case, use Docker. I don’t know what the version of Docker is in Debian but in Ubuntu 22.04 LTS, it’s recent enough so you don’t have to f around with third party repos.
Take a distro with a package manager you are familiar with. Debian should do it.
And try out docker it’s really easy to learn and straight forward.
Jellyfin has a well documented docker compose.yml which is just a textfile that points out the facts like used versions, environment and volume paths.
I did a transition from my docker compose tools to a new system in under an hour yesterday. All I had to do was backup the volumes or data paths. Firing up the containers looks like a new install but it’s just downloading the container and everything runs like before without losing any config.
Funnily enough, I use FreeBSD. It’s simple and easy. Native zfs is perfect for lots of media. I only forgo hw acceleration but don’t miss it at all
deleted by creator
I use appjails to containerise my apps like jellyfin, it’s similar to docker but simpler and more powerful (docker does not support freebsd)