Running Docker on a cheap VPS is completely viable — but the phrase “cheapest VPS” can lead you somewhere painful. The Docker daemon itself is lean. What gets you is the RAM footprint of everything running inside it. This guide gives you honest sizing guidance and the three budget providers that hold up in practice.
How Much VPS Does a Docker Stack Actually Need?
Docker’s daemon idles at around 100–200 MB of RAM. That sounds fine until you add containers on top. Here’s a practical sizing table:
| Workload | Containers | Minimum RAM | Recommended RAM |
|---|---|---|---|
| Single lightweight service | Nginx, a static site, or a small bot | 512 MB (with swap) | 1 GB |
| Two small services | Reverse proxy + one app | 1 GB (with swap) | 2 GB |
| Typical self-hosted stack | App + database + reverse proxy | 2 GB | 4 GB |
| Full homelab stack | Nextcloud, n8n, monitoring, etc. | 4 GB | 8 GB |
A few things that catch people off guard:
Image pulls spike RAM. Pulling a large image (Postgres, a Node app) temporarily spikes memory and disk I/O. On a 1 GB box with other containers running, this can trigger OOM kills.
Databases are the hidden cost. A container running a static site is tiny. The same app backed by Postgres or MariaDB needs memory for the database engine, its caches, and your application simultaneously.
NVMe storage matters more than it looks. Pulling images, overlayfs operations, and any database writes all hit disk hard. HDD-backed VPS plans — still common at the cheapest price tiers — can make image pulls sluggish and hurt database-heavy apps like Nextcloud.
Always enable swap on small boxes. A 1–2 GB swap file costs you nothing extra and prevents sudden OOM kills during off-peak spikes. It is not a substitute for enough RAM under sustained load, but it is a meaningful safety net for bursty workloads.
The Cheapest VPS Picks for Docker
Hetzner — Best Budget Value
Hetzner is the default recommendation for budget Docker hosting in Europe and increasingly in the US (Ashburn datacenter). Their CX22 plan (2 GB RAM, 2 vCPUs, 40 GB NVMe) sits at a price point that undercuts most competitors while offering NVMe storage and generous bandwidth. If you want a real Docker Compose stack — a reverse proxy, an app, and a database — start here.
The catch: datacenters are in Germany, Finland, and the US East Coast. If you need low latency in Asia-Pacific or the US West, Hetzner is not the answer.
Vultr — Best for Global Locations
Vultr has 25+ datacenter locations worldwide, which makes it the go-to choice when your users are spread across regions or when you specifically need a datacenter near a particular geography. Their High Performance plans (NVMe-backed) are slightly pricier than Hetzner but comparable to DigitalOcean with better value per dollar at entry tiers.
For Docker workloads, pick the High Performance tier over the regular Cloud Compute tier — the NVMe difference is real for image pulls and database I/O.
Hostinger — Cheapest Entry Point
Hostinger KVM 1 (1 GB RAM) is the cheapest KVM VPS available from a provider that isn’t a reliability gamble. It works for a single container: a Wireguard VPN, a simple web app, a small bot. It does not work well for multi-container stacks. Enable swap, keep your workload to one real service, and it holds up.
Upgrade to Hostinger KVM 2 (2 GB RAM) if you want more headroom without leaving the platform.
When the Cheapest Tier Isn’t Enough
The absolute cheapest VPS tier — typically 512 MB RAM — exists and technically installs Docker. In practice it is miserable for container workloads. The daemon itself barely fits, image pulls can OOM-kill running containers, and any database engine will be in constant swap contention.
The sweet spot for real Docker use is 2 GB RAM with NVMe storage. That covers a solid two- or three-container stack and leaves room for updates and restarts. Going below that is a trade-off you can make for a single, static-memory service — just do it with open eyes.
Where to Go From Here
If you are still deciding which VPS provider fits your wider self-hosting needs, the best VPS for self-hosting breakdown covers more providers across more use cases.
Once you have a box provisioned, two common Docker stacks to deploy first: self-hosting Nextcloud for your own cloud storage, and self-hosting n8n for workflow automation — both run comfortably on a 2–4 GB VPS with Docker Compose.
