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.
No low-effort posts. This is subjective and will largely be determined by the community member reports.
Resources:
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
Running 50 on one machine, four on my fileserver and another on a hacked up hp eliteone (no screen) which runs my 3d printer. Believe my immich container is a nspawn under nixos too.
Some are a wip but the majority are in use. Mostly internal services with a couple internet facing, I've got a good backlog of work to do on some with some refactoring my nixos configs for many too 😅.
From my Erying ES system:
59 according to docker info.
Hot damn. That is a far better way then counting the lines from docker ps
I recently went from 0 to 1. Reinstalled my VPS under debian, and decided to run my forgejo instance with their rootless container. Mostly as a learning experience, but also to easily decouple the forgejo version from whichever version my distro packages.
Right now I'm at 33 with 3 stopped I haven't used in a while. Also got 3 VMs running. A handful are duplicates eg redis/postgresql/photon/caddy
40 containers behind traefik, but I did just add a new sablier middleware to stop when iddle and start when first requested. Electricity is not cheap for me. But i got lucky to add 64GB RAM in my NAS and 128GB Ram in Desktop last march because prices went crazy
but I did just add a new sablier middleware to stop when iddle and start when first requested.
Would you mind expounding on this? Electricity is fairly affordable in my locale, however I've been on a mission to cut out consumption when it's not needed. Have you noticed an ROI?
How it started : 0
Max : 0
Now : 0
Iso27002 and provenance validation goes brrrrr
31 Containers in all. I have been up as high as ~60 and have paired it back removing the things I wasn't using.
I also tend to remove anything that uses appreciable CPU at idle and I rarely run applications that require further containers in a stack just to boot, my needs aren't that heavy.
My containers are running containers... At least 24.
Zero.
About 35 NixOS VMs though, each running either a single service (e.g. Paperless) or a suite (Sonarr and so on plus NZBGet, VPN,...).
There's additionally a couple of client VMs. All of those distribute over 3 Proxmox hosts accessing the same iSCSI target for VM storage.
SSL and WireGuard are terminated at a physical firewall box running OpnSense, so with very few exceptions, the VMs do not handle any complicated network setup.
A lot of those VMs have zero state, those that do have backup of just that state automated to the NAS (simply via rsync) and from there everything is backed up again through borg to an external storage box.
In the stateless case, deploying a new VM is a single command; in the stateful case, same command, wait for it to come up, SSH in (keys are part of the VM images), run restore-<whatever>.
On an average day, I spend 0 minutes managing the homelab.
Is this in a repo somewhere we can have a look?
I'll DM you... Not sire I want to link those two accounts publicly 😄
On an average day, I spend 0 minutes managing the homelab.
0 is the goal. Well done !
74 across 2 proxmox nodes in a few lxcs
64 containers in total, 60 running - the remaining 4 are Watchtowers that I run manually whenever I feel like it (and have time to fix things if something should break).
There is a post about getting overwhelmed by 15
I made the comment 'Just 15' in jest. It doesn't matter to me. Run 1, run 100. The comment was just poking the bear as it were. No harm nor foul intended. Sorry if it was received differently.
I am like Oprah yelling “you get a container, you get a container, Containers!!!” At my executables.
I create aliases using toolbox so I can run most utils easily and securely.
Toolbox?
Edit: Oh cool! Thanks for sharing.
https://github.com/containers/toolbox
Podman toolboxes, which layer a do gained over your user file system, allowing you to make toolbox specific changes to the system that only affect that toolbox.
I think it’s oringinally meant for development of desktop environments and OS features, but you can put most command line apps in them without much feauture breakage.
I always saw them pitched by Fedora as the blessed way to run CLI applications on an immutable host.
That’s why I use them, but they are missing the in ramp to getting this working nicely for regular users.
E.g. how do I install neovim with toolbox and get Wayland clipboard working, without doing a bunch of manual work? It’s easy to add to my ostree, but that’s not really the way it should be.
I ended up making a bunch of scripts to manage this, but now I feel like I’m one step away from just using nixos.
None, if it's not in a Debian repo I don't deploy it on my stable server.
It's not really about docker itself, I just don't think software has married enough if it's not packaged properly
My kubernetes cluster is sitting happily at 240, and technically those are pods some of which have up to 3 or 4 containers, so who knows the full number.
35 stacks 135 images 71 containers
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?
100 containers isn’t really a lot. Projects often use 2-3 containers. Thats only something like 30-50 services.
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.
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...
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
36, with plans for more
140 running containers and 33 stopped (that I spin up sometimes for specific tasks or testing new things), so 173 total on Unraid. I have them gouped into:
I subscribe to all their github release pages via FreshRSS and have them grouped into the Auto/Manual categories. Auto takes care of itself and I skim those release notes just to keep aware of any surprises. Manual usually has 1-5 releases each day so I spend 5-20 minutes reading those release notes a bit more closely and updating them as a group, or holding off until I have more bandwidth for troubleshooting if it looks like an involved update.
Since I put anything that might cause me grief if it breaks in the manual group, I can also just not pay attention to the system for a few days and everything keeps humming along. I just end up with a slightly longer manual update list when I come back to it.
I’ve never looked into adding GitHub releases to FreshRSS. Any tips for getting that set up? Is it pretty straight forward?
I just added this URL for Jellyfin and it "just worked":
if not, adding .rss or .atom should do the trick:
https://github.com/jellyfin/jellyfin/releases.atom https://github.com/jellyfin/jellyfin/releases.rss
Agreed. Im tired after work. Debian/yunohost is good enough.
At work its hundreds of docker containers but all ci/cd takes care of that.
I salute you and wish you the best in never having a dependency conflict.
I've been resolving them since the late 90s, no worries.
Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I've seen in this thread:
| Fewer Letters | More Letters |
|---|---|
| NAS | Network-Attached Storage |
| Plex | Brand of media server package |
| SSH | Secure Shell for remote terminal access |
| SSL | Secure Sockets Layer, for transparent encryption |
| VPN | Virtual Private Network |
| VPS | Virtual Private Server (opposed to shared hosting) |
| k8s | Kubernetes container management package |
7 acronyms in this thread; the most compressed thread commented on today has 8 acronyms.
[Thread #42 for this comm, first seen 29th Jan 2026, 11:00] [FAQ] [Full list] [Contact] [Source code]
13 running on my little Synology.
Actually more than I expected, I would have guesses closer to 8
I have currently got 23 on my n97 mini pc and 3 on my raspberry pi 4, making 26 in total.
I have no issues managing these. I use docker compose for everything and have about 10 compose.yml files for the 23 containers.
About 62 deployments with 115 "pods"
9 containers of which 1 is container manager with 8 containers inside (multi-containers counted as 1). And 9 that are installed off the NAS app store. 18 total.