Submitted 2 weeks ago by slazer2au@lemmy.world to selfhosted@lemmy.world
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.
140 running containers and 33 stopped (that I spin up sometimes for specific tasks or testing new things), so 173 total on the 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":
I added the bookmarklet to my bookmarks bar so it’s pretty easy to just navigate to the releases page on github and hit the button. I change the “visibility” setting to “show in its category” so things stay in their lanes rather than all go in a communal main feed but otherwise leave it as default.
I did have to add some filters to the categories so it wouldn’t flag all the -dev/-rc releases but that’s it. The filters that work for me are:
intitle:prototype- intitle:-build-number intitle:rc5 intitle:rc6 intitle:rc7 intitle:rc8 intitle:rc9 intitle:-dev. intitle:Beta intitle:preview- intitle:rc1 intitle:rc2 intitle:rc3 intitle:rc4 intitle:"Release Candidate" intitle:Alpha intitle:-rc intitle:-alpha intitle:-beta intitle:develop- intitle:"Development release" intitle:Pre-Release
0, it’s all organised nicely with nixos
Boooo, you need some chaos in your life.
That’s why I have one host called theBarrel and it’s just 100 Chaos Monkeys and nothing else
I have 1 podman container on NixOS because some obscure software has a packaging problem with ffmpeg and the NixOS maintainers removed it. docker: command not found
I know using work as an example is cheating, but around 1400-1500 to 5000-6000 depending on load throughout the day.
At home it’s 12.
I was watching a video yesterday where an org was churning 30K containers a day because they didn’t profile their application correctly and scaled their containers based on a misunderstanding how Linux deals with CPU scheduling.
Yeah that shit is more common than people think.
A big part of the business of cloud providers is that most orgs have no idea how to do shit. Their enterprise consultants are also wildly variable in competence.
There was also a large amount of useless bullshit that I needed to cut down since being hired at my current spot, but the amount of containers is actually warranted. We do have that traffic, which is both happy and sad, since while business is booming, I have to deal with this.
Zero. Either it’s just a service with no wrappers, or a full VM.
Why a full VM, that seems like a ton of overhead
For some convoluted networking things it’s easier for me to have a full “machine” as it were
Zero.
About 35 VMs though, each running either a si gle 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.
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.
Why VMs instead of contsiners? Seems like way more processing overhead.
Eh… Not really. Qemu does a really good job with VM virtualizarion.
I believe I could easily build containers instead of VMs from the nix config, but I actually do like having a full VM: since it’s running a full OS instead of an app, all the usual nix tooling just works on it.
Also: In my day job, I actually have to deal quite a bit with containers (and kubernetes), and I just… don’t like it.
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 !
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.
How it started : 0
Max : 0
Now : 0
Iso27002 and provenance validation goes brrrrr
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 |
| k8s | Kubernetes container management package |
[Thread #42 for this comm, first seen 29th Jan 2026, 11:00] [FAQ] [Full list] [Contact] [Source code]
None. I run my services they way they are meant to be run. There is no point in containers for a small setup. Its kinda lazy and you miss out on how to install them.
Small setups can very easily turn into large setups without you noticing.
The only bare-metal setup I’d trust to be scaleable is Nix flakes (which I’m actually very interested in migrating to at some point)
I’ve never even heard of NIX flakes before today. It looks like another soluion in search of a problem. I trust debian and I trust bare metal more than any container setup. I run multiple services on one machine. I currently have two machines to run all my services. No problems and no downtime other than a weekly update and reload. All crontabed, all automatic.
At work I have multiple services all running in KVM including some windows domain controllers. Also no problem and weekly full backups are a worry free. Only requiring me to checks them for consistency.
In short as much as people try to push containers they are only useful if you are dealing with more than few services. No home setup should be that large unless someong is hosting for others.
I still haven’t figured out containers. 🙁
How come? What do you use to run them and what is it you have a hard time with?
I’m using docker. Tried to set up Jellyfin in one but I couldn’t for the life of me figure out how to get it to work, even following the official documentation. Ended up just running the jellyfin package from my distros repo, which worked fine for me. Also tried running a tor snowflake, which worked, but there was some issue with the NAS being restricted and I couldn’t figure out how to fix that. I kinda gave up at that point and saved the whole container thing to figure out another day. I only switched to Linux last year, so I’m still pretty new to all of this.
Am not using docker yet. Currently I just have one Proxmox LXC, but am planning on selfhosting a lot more in the near future…
Awesime! I like ProxMox. Check out the Helper Scripts if you haven’t already. Some people like them, some don’t.
59 according to docker info.
Hot damn. That is a far better way then counting the lines from docker ps
Hot damn
That literally got a snort, because I feel the same way when I find a much easier/cleaner way of doing something.
44 containers and my average load over 15 min is still 0,41 on an old Intel nuc.
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.
I have 43 running, and this was a great reminder to do some cleanup. I can probably reduce my count by 5-10.
two, one for running discord backup viewer webui and the other for archiveteam warrior containers
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.
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 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.
yes as most service sleep, and time to spin them up is fast. Moreover some services continuously poll folders and avoid disks to sleep. Letting disks sleep the whole night is a good idea if not in use, this won’t shorten their lifespan.
I wouldn’t expect it to matter much, idle processes are pretty cheap.
Well the containers are grouped into services. I would easily have 15 services running, some run a separate postgres or redis while others do an internal sqlite so hard to say.
If we’re counting containers then between Nextcloud and Home Assistant I’m probably over 20 already lol.
11 running on my little N150 box. Barely ever breaks a sweat.
At my house around 10 For lemmy.ca and our other sites, 35ish maybe. At work… hundreds.
61 containers in 26 docker files.
49, I could imagine running all of those bare would be hard with dependencies
12 LXCs and 2 VMs on proxmox. Big fan of managing all the backups with the web ui (It’s very easy to back to my NAS) and the helper scripts are pretty nice too. Nothing on docker right now, although i used to have a couple in a portainer LXC.
I don’t use them. I’m using OpenBSD on my server which don’t support this feature.
No jails?
It’s FreeBSD feature
13 with podman on openSUSE MicroOS.
i used to have a few more but wasn’t using them enough so i cut them.
I’m running 3 or 4 I think… I’m more into dedicated VMs for some reason, so my important things are running in VMs in a proxmox cluster.
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).
What tool is that screenshot from?
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.
neidu3@sh.itjust.works 2 weeks ago
slazer2au@lemmy.world 2 weeks ago
I salute you and wish you the best in never having a dependency conflict.
neidu3@sh.itjust.works 2 weeks ago
I’ve been resolving with them since the late 90s, no worries.
RIotingPacifist@lemmy.world 2 weeks ago
I used Debian
Urist@lemmy.ml 2 weeks ago
My worst dependency conflict was a libcurlssl error when trying to build on a precompiled base docker image.
possiblylinux127@lemmy.zip 2 weeks ago
Isn’t that harder?
thinkercharmercoderfarmer@slrpnk.net 2 weeks ago
It depends a lot on what you want to do and a little on what you’re used to. It’s some configuration overhead so it may not be worth the extra hassle if you’re only running a few services (and they don’t have dependency conflicts). IME once you pass a certain complexity level it becomes easier to run new services in containers, but if you’re not sure how they’d benefit your setup, you’re probably fine to not worry about it until it becomes a clear need.
mesamunefire@piefed.social 2 weeks ago
Agreed. Im tired after work. Debian/yunohost is good enough.
Arghblarg@lemmy.ca 2 weeks ago
Me too!