Lima v2.3 shipped November 8 and it’s the most significant release the CNCF’s Linux VM manager has had in years. The headline: Lima now runs on Windows natively — no QEMU, no Unix toolchain. A new HCS driver talks directly to the Windows Host Compute System, the same virtualization layer that powers WSL2. The same release closes Linux’s long-standing networking gap versus macOS and adds a terminal UI.
What Lima Is (and Why You Should Care)
Lima (“Linux virtual Machines”) is the open-source VM manager that powers Colima, Rancher Desktop, and Podman Desktop under the hood on macOS. You write a YAML template, run limactl start, and Lima hands you a Linux shell with your home directory mounted and ports forwarded. It’s Docker Desktop without the license fees and without the GUI you never asked for.
Until v2.3, Lima was primarily a macOS story. Windows support existed but required QEMU — a reasonable ask on macOS, an annoying ask on Windows where most developers don’t have a Unix toolchain handy. Linux support existed but had a persistent gap: advanced networking only worked on macOS. Both gaps close in this release.
Windows: The HCS Driver
The new hcs driver joins the existing wsl2 and qemu options. Install Lima on Windows:
winget install Lima.LimaThen start a VM with the new driver:
limactl start --vm-type=hcs defaultThe HCS driver talks to the Windows Host Compute System API directly — the same thing WSL2 sits on. That means no QEMU installation, no Cygwin, nothing. If you’re already running WSL2, the hardware virtualization is already enabled. You need to add your user to the Hyper-V Administrators group and run limactl from an elevated shell, but that’s a one-time setup.
The honest caveat: this is experimental. The HCS driver currently supports plain mode only, which means no automatic file mount and no dynamic port-forwarding. You can copy files manually or forward ports by hand. For teams that just want a Linux shell on Windows to run scripts and daemons, it’s enough. For teams that need full file sync, hold off for now or use the wsl2 driver in the meantime.
HCS is tested on Windows 11 x86_64 only. If you’re on ARM or an older Windows version, the wsl2 driver is still your best option. See the HCS driver documentation for the full requirements list.
Linux: Networking Parity With macOS
macOS Lima users have had socket_vmnet for years — a networking helper that gives each VM its own IP address the host can reach directly. Linux had no equivalent, so lima:shared, lima:host, and lima:bridged network types simply didn’t work on Linux hosts.
v2.3 ships lima-privileged-net, a new helper that creates Linux bridges per VM, assigns gateway addresses, and cleans up after itself. The one-time setup:
limactl sudoers | sudo tee /etc/sudoers.d/lima
limactl start --network=lima:shared myvmYour VM gets a real IP address the host can reach. This matters if you’re running multiple VMs for Kubernetes dev clusters or service mesh testing on Linux — workflows that macOS users have done with Lima for a while but Linux users had to work around.
Two Quality-of-Life Additions
limactl menu: Running limactl with no arguments on an interactive terminal now launches a menu-driven TUI. Lima’s discoverability has always been a barrier for developers who aren’t already familiar with it. A menu that lets you start, stop, shell, and delete VMs without memorizing subcommands is a real improvement for occasional users.
–sync-exclude for AI sandboxes: limactl shell --sync now accepts --sync-exclude flags (rsync-style patterns) so you can keep .env files and node_modules out of the VM. You can also drop a .limasyncignore file in your project directory for the same effect. This is a direct response to developers using Lima VMs as sandboxes for AI coding agents — Codex and Claude Code running inside a Lima VM should not be able to reach your AWS keys.
limactl shell --sync --sync-exclude='.env' --sync-exclude='node_modules' myvmThe Downstream Story
The bigger implication is what happens to Colima, Rancher Desktop, and Podman Desktop. All three use Lima as their VM backend on macOS. As they ship or improve their Windows builds, they inherit Lima’s HCS driver support. A release that improves Lima’s Windows story is a release that improves the entire free Docker Desktop alternative ecosystem on Windows — which still largely depends on WSL2 and has limited VM configuration flexibility.
Upgrade on macOS with brew upgrade lima. On Linux and Windows, grab the latest via your package manager or winget upgrade Lima.Lima. The full release notes on GitHub list every change. The official announcement is on the CNCF blog.
