this post was submitted on 29 Jan 2026
118 points (97.6% liked)
Selfhosted
60210 readers
970 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:
-
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.
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!
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
All of you bragging about 100+ containers, please may in inquire as to what the fuck that's about? What are you doing with all of those?
In my case, most things that I didn't explicitly make public are running on Tailscale using their own Tailscale containers.
Doing it this way each one gets their own address and I don't have to worry about port numbers. I can just type http://cars/ (Yes, I know. Not secure. Not worried about it) and get to my LubeLogger instance. But it also means I have 20ish copies of just the Tailscale container running.
On top of that, many services, like Nextcloud, are broken up into multiple containers. I think Nextcloud-aio alone has something like 5 or 6 containers it spins up, in addition to the master container. Tends to inflate the container numbers.
Ironic that Nextcloud AIO spins up multiple...
Possibly. I don't remember that being an option when I was setting things up last time.
From what I'm reading it's sounding like it's just acting as a slightly simplified DNS server/reverse proxy for individual services on the tailnet. Sounds Interesting. I'm not sure it's something I'd want to use on the backend (what happens if Tailscale goes down? Does that DNS go down too?), but for family members I've set up on the tailnet, it sounds like an interesting option.
Much as I like Tailscale, it seems like using this may introduce a few too many failure points that rely on a single provider. Especially one that isn't charging me anything for what they provide.
A little of this, a little of that...I may also have a problem... >_>;
The List
QuickstartDatabases
Database Admin
Database Exporters
Networking Admin
Legally Acquired Media Display
Education
Books
Storage
Archival Storage
Backups
Monitoring
Metrics
Cameras
HomeAuto
Specific Tasks
Other
Plus a few more that I redacted.
I look at this list and cry a little bit inside. I can't imagine having to maintain all of this as a hobby.
From a quick glance I can imagine many of those services don't need much maintenance if any. E.g. RickRoll likely never needs any maintenance beyond the initial setup.
Dococd + renovate goes brrr
Not bragging. It is what it is. I run a plethora of things and that's just on the production server. I probably have an additional 10 on the test server.
Things and stuff. There is the web front end, API to the back end, the database, the redis cache, mqtt message queues.
And that is just for one of my web crawlers.
/S
Kube makes it easy to have a lot, as a lot of things you need to deploy on every node just deploy on every node. As odd as it sounds, the number of containers provides redundancy that makes the hobby easy. If a Zimaboard dies or messes up, I just nuke it, and I don't care whats on it.
100 containers isn’t really a lot. Projects often use 2-3 containers. Thats only something like 30-50 services.
"Only"