You can now run same OCI images as containers or Firecracker microVMs

ranger_danger

Where does the microvm kernel/initrd come from? How can it be built? I just want a system that's as easy as "docker run ubuntu" but launches as a microvm instead, without me having to source a kernel or remember hugenormously long qemu incantation lines.

vaylian

Sweet. I had hoped for someone to make a p2p container registry eventually. There is too much centralization with the current popular registries.

aliasxneo

Is the OP the author of this? Because they are writing responses here that are unquestionably unedited LLM generated responses. The project looks cool, and I'm particularly glad to see a reach for a p2p container registry, but that sort of behavior doesn't lend credibility to something as critical as image infrastructure.

miladyincontrol

"memmap2" link in readme is broken btw, I think your llm means memmap-rs

Izmaki

> Why this matters: Modern infrastructure uses too many execution engines — Docker for dev, containerd for production, Firecracker for isolation, CRI for Kubernetes, MCP agents for AI. It is my understanding that Docker Engine adds capabilities (such as network stack) on top of Containerd (which is a project maintained by the same people), and "CRI for Kubernetes" is a Container Runtime Interface which COULD be something other than Containerd but often is just Containerd. So in essence the reason why yet another runtime exists is that we have a runtime for containers (Docker/Containerd, Containerd and, for example, Containerd as the CRI in K8s), a runtime for isolation and a runtime for AI agents. That seems like an unnecessary argument on its own, which makes me wonder why it's listed as the first argument.