There is a post about getting overwhelmed by 15 containers and people not wanting to turn the post into a container measuring contest.
But now I am curious, what are your counts? I would guess those of you running k*s would win out by pod scaling
docker ps | wc -l
For those wanting a quick count.
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?
On an average day, I spend 0 minutes managing the homelab.
0 is the goal. Well done !
13 running on my little Synology.
Actually more than I expected, I would have guesses closer to 8
35 stacks 135 images 71 containers
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.
25, with your “docker ps” command, on my aging Nuc10 PC. Only using 5GB of its 16GB of RAM.
What, me worry?
51 containers on my Unraid server, but only 39 running right now
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
11 running on my little N150 box. Barely ever breaks a sweat.
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.
@slazer2au Application containers: 30-40
System containers (including kube, Istio, CNI, etc): ~20Shifting from Istio sidecar mode to Istio ambient mode made a big difference.
- There are usually one or two of those that are just experimental and might get trashed.
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?
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.
58, my cpu is usually around 10-20% usage. I really don’t have any trouble managing/maintaining these. Things break almost weekly but I understand how to fix them every time, it only takes a few minutes
I don’t have access to my server right now, but it’s around 20 containers on my little N100 box.
$ docker ps | wc -l 14Just running 13 myself.






