Selfhosted
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.
-
No spam.
-
Posts are to be related to self-hosting.
-
Don't duplicate the full text of your blog or readme if you're providing a link.
-
Submission headline should match the article title.
-
No trolling.
-
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.
-
AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
view the rest of the comments
If you already know Debian that's a big point in its favor. Nothing beats a distro you're familiar with. (And I'd make the same argument if you were used to Ubuntu.)
I've used both Debian and Ubuntu Server on my home servers and I ended up returning to Debian.
I've ended up concluding that Ubuntu Server is Debian, just with more quirks. It offers nothing essential that you can't do on Debian, and it will just complicate your life when the LTS support period eventually runs out (and even during LTS, when you have to jump through hoops like Ubuntu One to keep updates coming.)
(1) You can fuck up both Ubuntu and Debian's upgrades by adding a lot of 3rd-party repos because
aptdoesn't safeguard against external repos interfering with the core repos' dependency graph.So the trick is to keep the OS minimal, install only Docker from its repo and install anything else in Docker containers. That way you benefit the most from Debian being stable and very little from Ubuntu Server.
If you also need to run system containers and virtual machines you can add Incus later to the mix alongside Docker and still keep your host OS lean and simple.
You can also consider completely migrating to Proxmox later, which is also Debian under the hood but it's a more turnkey solution. I wouldn't recommend jumping straight into Proxmox unless you're fairly sure that you'd need to run VMs. (If you're unsure stick to plain Debian for now.)
Why from Docker's repo and not from Debian's? I just did a quick
apt search dockerand I seedocker.ioanddocker-cli.Debian's versions lag badly behind Docker's. You'd always be missing the latest features. Docker introduces them at a steady pace and it can get annoying to see people talking about a new useful improvement and then months passing before it gets to you.
Maybe I don't need the new features :)
You say that but sometimes they come up with stuff that's really useful and it can be very annoying to not have it. Like when they integrated compose into the main.
Also, if you later decide to switch to the official version you'll have to handle the upgrade carefully or you risk wiping out all your images, containers, networks, volumes etc. Which can be fine if you have backups of all the relevant functional definitions and the volumes and so on, but obviously a huge pain if it catches you unprepared.
Mind you, this can also happen by tinkering with stuff in
/etc/docker/daemon.json, which is how I originally learned to back up my shit.Ok, I will keep that in mind. I'm just wary of what you said earlier:
You're not the first person to tell me not to add too many external repositories on Debian for the same reason.
In Docker's case is a non-issue because they were careful to use completely different names for all their packages. It's only when the external repo uses the same names as the core that the dependency resolver can get confused.
Rant:
aptshould either completely forbid external repos from using core package names (like Arch does), or look at both the package name and repo URL when deciding if a package is the same, not just package name.I'm guessing that letting external repos "hijack" a package name was once upon a time seen as a feature and then they never got around to fixing it.