Podman + krun
microvmmicrovm-toolopen sourcePodman with the krun runtime, run an OCI container as a with the familiar podman CLI.
Podman + krun is Podman using libkrun as its OCI runtime (podman run --runtime krun), so a normal container command instead launches a hardware-isolated with its own kernel. It is the recommended low-friction way on Linux (and macOS via HVF) to get a real boundary from your existing container workflow, the same podman commands, upgraded from shared-kernel to isolation.
Strengths
- MicroVM isolation from the familiar podman CLI, one --runtime flag
- Recommended low-friction 'real boundary' path on Linux
- Free and open source
Limitations
- Inherits libkrun's in-process model (second wall not automatic)
- Needs virtualization support (KVM/HVF)
- microVM device model is more limited than a full container/VM
Files & editor
desktop-remoteThe container filesystem lives in a microVM; Remote-SSH in or edit inside.
How you get your project into the environment and edit it. Shared-kernel routes bind-mount host files for your desktop editor; own-kernel routes keep files in the guest, so a desktop editor attaches over remote, or you edit inside. Mounts and remote editing.