reShapr on apple/container: One VM per Container on Your Mac


Most of us build MCP servers and agents on a Mac. Until now, running reShapr on that Mac meant Docker Desktop or Podman. Containers need a Linux kernel, so these tools start one Linux VM and run every container inside it, sharing that kernel. The VM starts with the app and stays around while you work.
Apple ships a different model. apple/container is an open source tool, written in Swift, that runs each Linux container in its own lightweight VM on Apple silicon, with only small engine services resident when no container runs.
We added it to reShapr as a third engine: reshapr run --engine apple. Here is what that means, what we measured against Docker Desktop, and where it still falls short.
TL;DR reShapr 1.2.0 adds apple/container as a third engine (reshaprio/reshapr#620), selected with
--engine apple. It is not faster than Docker Desktop. It costs almost nothing when idle and isolates each container in its own VM. The numbers below come from reShapr 1.2.0. The proof of concept ran the same stack on 1.1.0 and 1.1.1 before the release.
