MicroVM Dev Container Setup With Real VS Code Integration and Working Docker-In-VM

dev tool real project • single request

Power devs want their local dev container experience but inside a microVM for security and to actually run Docker without the docker-in-docker pain. Existing microVM tools (Firecracker, Lima, krunvm) target ephemeral workloads or don't integrate cleanly with VS Code's remote dev extension. Docker's new sandboxes are AI-agent-only and not user-customizable.

builder note

The shortest path is a thin opinionated wrapper on Lima or krunvm: a single 'devvm up' that stamps out a persistent microVM, mounts your repo, runs containerd inside, and registers a VS Code remote endpoint. Sell the secrets-via-vsock part as the differentiator.

landscape (5 existing solutions)

Each tool nails one corner — Lima's VS Code path, Firecracker's isolation, Docker's polish — but nobody ships the full 'Dev Container UX + microVM isolation + working Docker inside + secrets' combo as one product.

Lima Aimed at Docker Desktop replacement on Mac — works but VS Code Dev Container UX layer is DIY and Docker-in-Lima-in-VM has rough edges.

Firecracker / Ignite Great for serverless and ephemeral; not designed for long-lived persistent dev environments with mounted host folders.

Docker Sandboxes Locked to AI-agent flows, not bring-your-own-image.

Coder / Gitpod Cloud-first; the user explicitly wants local microVM, not a cloud workspace.

Dagger Powerful but a build pipeline, not a 'mount my host folder and edit in VS Code' day-to-day.

sources (1)

hn https://news.ycombinator.com/item?id=47898711 "Tons of different solutions and none of them seem to work." 2026-04-25

microvmdev-containervscodedocker-in-dockerisolation