- macOS gains native container‑machine capability.
Apple’s official documentation, container‑machine.md, published on June 10, 2026, describes a new subsystem that lets developers define and run lightweight container images directly on the host OS. The file lives in the Apple/container repository and is titled “Container Machine”.
The docs show a JSON‑based manifest (container-machine.json) that specifies the base image, CPU limits, and file system layers. When executed, the system spins up a minimal VM using the built‑in hypervisor, reports start‑up times of roughly 1.2 seconds for a 200 MB image, and claims a 15 % reduction in memory overhead compared with running full‑size Docker containers on macOS.
If you need to use existing Docker images, Apple notes the feature is not a wrapper for Docker Desktop; it is its own runtime. That means third‑party tools must be updated to target the new API rather than relying on Docker’s engine.
The addition matters because macOS developers can now test containerised workloads without installing separate virtualization tools, tightening the feedback loop for cloud‑native apps. It also gives Apple a foothold in the container market beyond the usual CLI utilities.
For now the feature is limited to Apple‑silicon Macs and requires macOS 15.0 or later; older Intel Macs will not see it until Apple releases a compatible version.