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

One app image, two lives — and the comments instantly turned into a trust fight

TLDR: Pullrun says one app image can now run as either a standard container or a more isolated tiny virtual machine, which could simplify how software gets deployed. Commenters loved the convenience and peer-to-peer sharing idea, but the thread quickly turned into questions about missing details, overselling, and AI-written replies.

A new tool called Pullrun just rolled in with a big, crowd-pleasing promise: make one app package run either like a normal container or inside a tiny virtual machine, with no extra packaging headache. In plain English, it’s pitching a future where developers stop juggling a pile of different tools just to run the same software in different places. It’s tiny, fast, and says it can spread app files around a cluster peer-to-peer, which had some readers practically cheering from the back row. One fan was basically screaming, finally, saying they’d been waiting for a peer-to-peer app registry because today’s setup feels way too centralized.

But this thread did what tech threads do best: it immediately became a drama factory. One of the loudest reactions was less “wow” and more “okay, but where’s the magic virtual machine part actually coming from?” A commenter wanted the dream setup: as easy as typing one simple command, without hunting down a special kernel or memorizing nightmare launch commands. Then came the trust issue. Another user accused the project author of posting responses that looked painfully AI-generated, and suddenly the vibe shifted from shiny demo excitement to “do we trust this for core infrastructure?” Ouch.

And yes, the nitpick squad arrived right on time. One person called out a broken link in the readme and joked that the author’s AI probably meant a different library. Another challenged the project’s explanation of the existing tool mess, basically saying the pitch oversimplified how today’s container world actually works. So the mood is clear: people love the idea, want the convenience, but are already side-eyeing the details.

Key Points

  • Pullrun is presented as a 12 MB single-binary OCI runtime that can run the same OCI image as either a container or a VM.
  • The article says Pullrun uses a content-addressed DAG store instead of overlayfs, enabling deduplication and zero-copy mmap reads.
  • Pullrun advertises peer-to-peer image distribution so one registry pull can be shared across a cluster at LAN speed.
  • The same binary is described as including a Kubernetes CRI shim in beta, Docker Compose support, an MCP server, policy tools, P2P sync, and encrypted secrets.
  • The article includes install and quick-start examples for macOS, Linux, and Windows/WSL2, plus commands for pull, run, build, push, save, and load workflows.

Hottest takes

"that sort of behavior doesn’t lend credibility" — aliasxneo
"I had hoped for someone to make a p2p container registry eventually" — vaylian
"I just want a system that’s as easy as 'docker run ubuntu' but launches as a microvm instead" — ranger_danger
Made with <3 by @siedrix and @shesho from CDMX. Powered by Forge&Hive.