Member OP
My 1GB OVHcloud VPS now running 47 containers. Compose file is 800 lines. I know is bad. I know. But each service "essential" - monitoring, logging, reverse proxy, databases, bots, home automation bridge. Swap is 2GB and screaming. OOM kills daily. I am trapped by own success. Anyone escape this? I cannot afford upgrade, price in my country too high for bigger plan
Member
« 47 containers » on 1GB this is the Madness. The Docker it is not for this Scale. You need the Orchestrator or you need the Discipline. I try the Podman on my InterServer box, the Rootless it use less RAM, yes? 20% less in my Test. The Systemd with Quadlet, you know this? No Docker Daemon eating the Memory. Yes, I think this is your Path.
Member
¡47 containers is very insane! Hahaha I had 30 and my VPS died every night. I wrote long story about migrating to Podman but I deleted it, too messy. Short version: I'm using Podman + systemd now, rootless, no daemon. 300MB saved. Your compose files become systemd units, very clean. Hahaha but seriously, check which containers actually work. I bet half is "nice to have" not "need to have" ¿yes?
Member
Best Practices for Container Density at Scale
I've been running on Hetzner for a while and wanted to share what I've learned evaluating architecture against these criteria:
• Memory overhead per container runtime
• Shared library deduplication
• Init system integration
Current OVHcloud 1GB Plan Specifications:
- 1 vCPU
- 1GB RAM
- 25GB SSD
- 1TB Transfer
For 47 workloads, vertical scaling or workload consolidation is recommended. Podman with systemd unit generation (quadlet) reduces daemon overhead significantly in my experience.
— harbourops
Rootless podman saves 300MB? On a 1GB box that's still 47 containers.
