Three answers to "where does the Linux kernel come from?"

All three solve the same problem: macOS has no Linux kernel, so running Linux containers means getting one somewhere. They solve it differently enough that "which is fastest" undersells the difference. Docker Desktop and OrbStack run every container inside one shared Linux VM. Apple's tool, stable at 1.0 since June 2026, gives each container its own lightweight VM on the Virtualization framework, the design described in the companion post.

What Apple's tool gets right

  • Stronger isolation by default. With a VM per container, a kernel-level compromise in one container doesn't automatically reach the others. It's the container-versus-VM distinction from the security deep dive, except here it comes with the default configuration.
  • Fast at what it's built for. A minimal kernel with a small Swift init process is reported to boot in under a second, tuned for starting one container quickly.
  • Free and open source, with no commercial catch. Apache-licensed, with no company-size threshold like Docker Desktop's and no personal-versus-work split like OrbStack's.
  • OCI-compatible. Docker Hub images run unmodified, and what you build pushes to any standard registry.

What the 1.0 still lacks

A 1.0 isn't feature-complete. Apple's tool is Apple silicon only, with no path for Intel Macs. There's no Docker Compose equivalent for multi-container setups and no confirmed native Kubernetes integration, both real gaps if your workflow depends on them. And it's new, with a far smaller body of tutorials, answers and CI integrations than Docker has built up over a decade. That doesn't make it a bad tool; it makes it a young one.

Where Docker Desktop and OrbStack still win

The full comparison covers both. In short: Docker Desktop is still the default that every tutorial, CI config and onboarding doc assumes, with by far the largest ecosystem, and its own newer VM backend (Docker VMM) aimed at closing the performance gap. OrbStack publishes substantial filesystem speed advantages over Docker Desktop's default backend on small-file and metadata-heavy work; test them against your own workload, but they reflect a real strength. Both also run on Intel Macs.

Which to reach for

  • Deep in Docker's ecosystem (Compose, Kubernetes, CI built around it): stay on Docker Desktop. The migration isn't worth it yet.
  • Want the fastest file performance for a container-heavy local workflow: try OrbStack against your own workload before paying.
  • Want free, strongly isolated containers on Apple silicon, without Compose or Kubernetes: Apple's container fits well. Budget for a smaller ecosystem.

Related reading: Apple Containers vs. Linux VMs, the Docker Desktop and OrbStack comparison, and VM vs. container vs. sandbox on macOS. Or download Velo Workspaces and try it yourself.