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.
You must log in or # to comment.
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.
- Because I’m old, crusty, and prefer software deployments in a similar manner.
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.
I use Debian
Isn’t that harder?
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.
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 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 and started self-hosting last year, so I’m still pretty new to all of this.
If you do decide to look in to containers again and get stuck please make a post. We are glad to help out. A tip I can give you when asking for help. Tell the system you are using and how. Docker with compose files or portainer or something else etc. If using compose also add the yaml file you are using.
I will definitely try again at some point in the next year, so I will keep that in mind! I appreciate the kind words. A lot of what you said is over my head at the moment though, so I’ve got my work cut out for me. 😅
I’m pretty sure I was at the same point years ago. The good thing is, next time you look into containers it’ll likely be really easy and you’ll wonder where you got stuck a year or two ago.
At least that’s what has happened to me more times than I can remember.
Haha, fingers crossed.
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
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’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.
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.
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.
Yeah, just wondered because containers just hook into the kernal in a way that doesn’t have overhead. Where as a VM has to emulate the entire OS. But hey I get it, fixing stuff inside the container can be a pain
On an average day, I spend 0 minutes managing the homelab.
0 is the goal. Well done !
Edit: Ha! Some masochist down-voted that.
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.
13 with podman on openSUSE MicroOS.
i used to have a few more but wasn’t using them enough so i cut them.
How it started : 0
Max : 0
Now : 0
Iso27002 and provenance validation goes brrrrr
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:
- 118 Auto-updates (low chance of breaking updates or non-critical service that only I would notice if it breaks)
- 55 Manual-updates (either it’s family-facing e.g. Jellyfin, or it’s got a high chance of breaking updates, or it updates very infrequently so I want to know when that happens, or it’s something I want to keep particular note of or control over what time it updates e.g. Jellyfin when nobody’s in the middle of watching something)
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 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-ReleaseI 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
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.
Exactly!
Portainer says 14 (including itself) 😅
I have about 15 trueNAS apps only 2 of them are custom (endurain and molly socket). They are containers but very low effort handled mostly by the system. I also have 3 LXC. And 2 VMs (home assistant and openWRT). I spend only few minutes a week on maintenance. And then I tinker for several hours a week, testing new apps or enhancing current ones configs.
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 before 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?
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.
In here it is .30 pro Kwh
In here it is .30 pro Kwh
Ouch!
I wouldn’t expect it to matter much, idle processes are pretty cheap.
yes and no…
- Idle process are not cheap: some processes avoid all disks to sleep. .
- In Europe electricity is not cheap, a bit more than .30 euro/kwh
Here’s what I’ve been doing: https://lemmy.world/post/42332816/21852448
I’ll check out sablier. Every little bit helps. Even tho it’s selfhosting, there’s no need to consume more than necessary.
What I’ve been doing is running a cron at a certain time in the evening, shutting down the server, and am working on a WOL sequence from my pfsense box fired by a cron, to crank it back up. Since it sits idle for 12 hours out of the 24, I just didn’t see a need to keep it sucking up electricity.
Of course, I’m not running any midnight, mass downloads of Linux iso’s, and I have no other users save myself. If I had users, I’d pass the hat.
