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.
- 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
My worst dependency conflict was a libcurlssl error when trying to build on a precompiled base docker image.
Zero. Either it’s just a service with no wrappers, or a full VM.
I don’t use them. I’m using OpenBSD on my server which don’t support this feature.
61 containers in 26 docker files.
I still haven’t figured out containers. 🙁
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!
3 that I’m actually using, on my “Home Server” (Raspberry Pi).
One day I will be migrating the work stuff on VPS over to Docker, and then we’ll see who has the most!
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.
Portainer says 14 (including itself) 😅
41 containers running on Rocky Linux over here
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.
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
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 disagree that Nix is a solution in search of a problem, in fact it solves arguably the two biggest problems in software deployment: dependency hell and reproducibility (i.e. the “It works on my machine” problem)
Every package gets access to the exact version of all the dependencies it needs (without needless replication like Flatpaks would have) and sharing a flake to another machine means you can replicate that exact setup and guarantee it will be exactly the same
Containers try to solve the same problems, and succeed to a somewhat decent extent, although with some overhead of course.
I’m not trying to criticize you or your setup at all, if Debian alone works for you, that’s fine. The beauty of open source and self hosting is that we can use whatever tools we want, however we want. I do though think it’s good practice to be aware of what alternatives are out there should our needs change, or should our tools change to no longer align with our needs.
All containers do that. Its nothing new just another implementation of the idea with its own idea about what is best. It only saves resources in the form of time if its a large scale operation and finally its just the last in a long line of similar solutions.
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
