30 containers on a 4 GB Raspberry Pi 4: how I stopped my services from fighting each other
retained text
Hey r/homelab, **Repo:** [https://github.com/sablierapp/sablier](https://github.com/sablierapp/sablier) (since October 2020) **Docs:** [https://sablierapp.dev](https://sablierapp.dev/) **The problem** My server is a Raspberry Pi 4 (4 GB) running 30 containers on an SSD and a 6 TB HDD. On a box this small, every service is everyone's neighbor: when Paperless runs OCR while the \*arr stack is busy, Home Assistant and Pi-hole get sluggish too. Most of these services sit idle most of the day, still taking RAM, CPU and disk. **What Sablier does** It starts a container when you open it through your reverse proxy, and stops it when nobody uses it. You get a waiting page while it boots. On my Pi, Transmission, Memos, Portainer and Speedtest only run when I use them. If stopping is too blunt, it can instead throttle an idle service's CPU, memory or disk I/O, and restore them the moment you open it. It works with Docker, Podman, Proxmox LXC, systemd, Kubernetes and Nomad, behind Traefik, Caddy, Nginx and others. **Why not an existing tool** Nothing like it existed when I started in 2020. ContainerNursery and Lazytainer came a year later. Compared to them, Sablier plugs into your existing reverse proxy and can throttle instead of stop. **Why it's relevant here** Most of us run more services than our hardware comfortably holds. Sablier lets idle ones step aside for the ones you're using. **AI disclosure** Written by hand from 2020 to early 2026. Since May 2026, I've used AI coding agents (mostly Claude Code) for features, tests, docs and bug hunting. I design the features and review every change. About 43% of this year's commits are AI co-authored. This post was also written with Claude's help.
document fetched 2026-10-29 00:39 · canonical https://reddit.com/r/homelab/comments/1xhffpr/30_containers_on_a_4_gb_raspberry_pi_4_how_i