46
submitted 8 months ago by faethon@lemmy.world to c/selfhosted@lemmy.world

So I have been running a fair amount of selfhosted services over the last decade or so. I have always been running this on a Ubuntu LTS distribution running on a intel NUC machine. Most, if not all of my services run in a docker container, and using a docker compose file that brings everything up. The server is headless. I connect over ssh into a tmux config so I am always ready to go.

Ubuntu has been my stable server choice over the years. I've made the upgrade from 16, 18, 20 and 22 LTS release and everything has kept working. I even upgraded the hardware (old NUC to a new NUC) and just imaged the disk from the old one onto the new machine, and the server kept chugging along quite nicely, after I configured the hardware (specifically the Intel QuickSync for hardware transcoding in the Plex container).

Since Ubuntu has been transitioning from a really open community driven effort into a commercial enterprise, I feel it may be time to look at other distributions. On the other hand, it will require a fair amount of work to make the switch. But if it needs to be done, than so be it. I guess I am looking for opinions on what Linux distribution would fit my particular use case, and am wondering what most of us here are running.

TLDR; What stable, long term supported Linux distributions do you recommend for a headless server running a stack of docker containers?

you are viewing a single comment's thread
view the rest of the comments
[-] Guenther_Amanita@feddit.de 69 points 8 months ago* (last edited 8 months ago)

Debian. I don't see much benefit of Ubuntu LTS compared to plain old Debian. It's exactly what you wanted.

Alternatively, AlmaLinux is a good choice if you like Red Hat stuff (RHEL clone), but the difference between Ubuntu LTS and Debian would be almost not noticeable for you I think.

[-] h3ndrik@feddit.de 16 points 8 months ago* (last edited 8 months ago)

And I would agree. I've been using Debian on my VPS with docker-compose etc for years. Would recommend it, too. And it's pretty similar to what you have now. There isn't much needed to swich around or learn.

And it is the textbook example of a successful, community driven distro.

[-] faethon@lemmy.world 10 points 8 months ago

It seems to be the most logical move to go from Ubuntu to Debian indeed. As I understand it maintains the core Linux system as I have it now (systemd / apt / stable kernel) while truly community driven. I have to look into transitioning into the latest stable Debian release.

[-] h3ndrik@feddit.de 9 points 8 months ago

I mean it's not only alike what you're currently using... It's the foundation of Ubuntu. Lots of packages are exactly the same.

And I think you'll find something very similar, just with the stuff missing that Ubuntu added on top, and you don't like anyways.

Hope you can move you containers and volumes without too much effort. I mean since you're starting over anyways you could also pause for a minute and think if you want to recreate something similar or switch to something different. There are other containerization techniques, podman, systemd-nspawn, you could do your server in a declarative approach with NixOS... But if you like what you have now, and don't want to learn something entirely new, I'd say Debian is probably your solution.

[-] iso@lemy.lol 4 points 8 months ago

“Ubuntu added on top” you mean Snap? No thanks :)

[-] h3ndrik@feddit.de 3 points 8 months ago

It's not the first strange decision they made. I think I finally switched from Ubuntu to Debian when they introduced the Amazon advertisements to the Unity desktop. That must have been 12.10 Quantal Quetzal. I've been happy since and didn't miss the odd business strategies they pushed in the time since...

[-] lemmyvore@feddit.nl 4 points 8 months ago* (last edited 8 months ago)

The only thing you need to watch out is the kernel.

Debian stable is on a 2-year release cycle (odd years). LTS kernels are released once a year, but Debian needs time to test each release thoroughly so they use the LTS kernel from the previous year. This means that by the time the next stable Debian comes out the kernel will be 3 years old.

Example: Debian 11 released in 2021 with kernel 5.10 (from 2020). By the time Debian 12 released in 2023, kernel 5.10 was 3 years old.

You can of course use backports to get a newer kernel but using backports defeats the purpose of using Debian stable. So please think very carefully whether you need recent kernel support for anything.

Docker and ZFS are the usual suspects but they tend to support a pretty wide array of kernel versions so they should not be a problem. Especially since you can install them from 3rd party repos. But please understand that releases from external repos are, again, not tested with stable.

There are other things that may need kernel support, for example I use the Samba and NFS drivers from the kernel, which need userland packages as well, so in their case you definitely want to stick to the official stable packages.

If you can't live with old Debian kernels then stick to Ubuntu. There's no inherent problem with Ubuntu and given that you have experience with it it might actually be the ideal choice for you. There's no substitute for a distro you know very well.

[-] faethon@lemmy.world 1 points 8 months ago

Ah, that is a good point. I am using 6.5.0 kernel atm, as part of the HWE (hardware enablement) package, which supports QuckSync / hardware encoding of my 12th gen intel processor. I did a quick search, but did not find HWE for Debian is that correct?

[-] lemmyvore@feddit.nl 1 points 8 months ago

HWE for Debian should be in the backports.

I haven't looked into it tbh, my Intel is 7th gen so I have no problem running with Debian's older kernel.

load more comments (10 replies)
this post was submitted on 14 Mar 2024
46 points (92.6% liked)

Selfhosted

40198 readers
693 users here now

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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. 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.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS