macrostack

Layer 3 · self-hosting reality check

What it actually takes to self-host Lima

The docs say 2 GB. In practice you want 4 GB per VM. Here is the honest version — real requirements, real monthly cost, what you will be maintaining, and the one thing that catches people out.

Usually reached from Docker Desktop alternatives, where Lima is one of the picks.

Wondering whether you need to at all? Is Docker Desktop free? — what the free tier actually allows, and where the wall is.

RAM — documented minimum2 GB
RAM — what it really needs4 GB per VM
CPU2 vCPU per VM
Disk100 GB default per VM, thin-provisioned
Monthly cost$0 — it runs on the machine you already own
Setup time20 minutes if you write your own template
How you install itbrew install lima, then `limactl start` with a YAML template
Ongoing maintenanceLow, but the templates are yours to keep working.
Where it stops scalingAs many local VMs as the host has RAM for. Single-machine by design.

The thing that catches people out

Lima is the layer Colima is built on, and choosing it means choosing to configure things Colima decides for you. That is the point — you get arbitrary Linux VMs rather than a container runtime — but people install it expecting a Docker Desktop replacement and find no Docker socket, because wiring that up is a template you write.

When not to self-host Lima

You want containers working in ten minutes. That is Colima's job, and Colima is Lima underneath.

Every guide here carries this section. A site that only ever tells you to self-host is selling something — the useful answer is sometimes no.

Other Layer 3 self-hosting guides

Common questions

How much RAM does Lima actually need?
4 GB per VM in practice. The documented minimum is 2 GB, which is the figure at which the process starts rather than the figure at which it works under real use. 2 vCPU per VM alongside it.
What does self-hosting Lima cost per month?
$0 — it runs on the machine you already own This is commodity VPS pricing and excludes your time, which is the larger cost for most people — budget for low, but the templates are yours to keep working.
How long does it take to set up Lima?
20 minutes if you write your own template, via brew install lima, then `limactl start` with a YAML template.
When should I NOT self-host Lima?
You want containers working in ten minutes. That is Colima's job, and Colima is Lima underneath.
What is the most common mistake when self-hosting Lima?
Lima is the layer Colima is built on, and choosing it means choosing to configure things Colima decides for you. That is the point — you get arbitrary Linux VMs rather than a container runtime — but people install it expecting a Docker Desktop replacement and find no Docker socket, because wiring that up is a template you write.
The Macrostack brief

New swaps, worth your inbox.

A short, occasional email when we add a high-intent alternative or ship a new head-to-head. No spam, no selling your address — unsubscribe in one click.