32GB is usually worth it for a Docker home server.

Yes, if you’re running more than a handful of containers.

Docker containers share the host kernel, but each one still needs its own memory for the application, dependencies, and cache. A few small containers (Pi-hole, a basic web server, a monitoring tool) can run fine on 16GB. But once you add databases, a media server, a reverse proxy, or anything that processes data, memory fills up fast.

The real problem isn’t just running out of RAM—it’s that when you do, the kernel starts swapping to disk. That makes everything sluggish, and for a server you expect to be responsive, that’s brutal. 32GB gives you enough headroom to avoid that situation, and with current RAM prices, it’s not a huge premium over 16GB.

If you’re building a server you want to just work for the next few years without tinkering, go 32GB. If you’re only running two or three lightweight containers and you’re sure you won’t expand, 16GB is fine. But “a few more containers” has a way of turning into twelve.

Don’t cheap out on RAM if you want your little server to stay snappy under load.