TL;DR / Key Takeaways
- Apple quietly launched Container Machines, their native answer to WSL and Docker on the Mac.
- This new tool offers shocking performance but comes with critical trade-offs.
The WSL Moment for macOS Has Arrived
Apple's Container Machines, unveiled at WWDC 2026, finally deliver macOS's answer to Windows Subsystem for Linux (WSL). This powerful, first-party solution provides lightweight, persistent Linux environments, meticulously optimized for Apple Silicon, building directly on the "Apple Container" project from WWDC 2025.
Setup is shockingly simple. Developers build any OCI-compatible image using a Dockerfile and Apple's `container build` command. A single `container machine create <image_tag> <name>` command then launches a full, persistent Linux environment in literally seconds, complete with a configurable 7 CPUs and 18 GB of memory (half your Mac's default).
The killer feature is automatic home directory sharing. This mounts the macOS user's entire home directory as read-write within the Linux VM. Developers can leverage native macOS tools and editors, compiling and testing code directly in Linux without any file transfers or synchronization hassles.
This seamless integration means no more cumbersome `scp` or `rsync` commands. Use VS Code on macOS, build your Bun application in an Ubuntu 24 Container Machine, and test it instantly, all from the same directory. Simply run `container machine run` to enter the interactive terminal, confirming your Linux environment with `uname -a`.
Under the Hood: Why It’s Not Just Docker
Container Machines fundamentally diverge from traditional containerization by adopting a micro-VM architecture. Each Linux environment runs in its own independent, lightweight virtual machine, leveraging Apple's Virtualization Framework. This provides robust VM-level security isolation and complete container failure isolation, enhancing reliability and predictability beyond shared-kernel models.
Docker Desktop, in contrast, traditionally runs multiple containers within a single, larger, shared Linux VM. This shared kernel model, while resource-efficient for many applications, offers less stringent isolation between individual containers. Apple’s method ensures each Container Machine operates with its own dedicated resources and isolated kernel space, preventing cross-container interference.
A key advantage for developers is the ability to run a full systemd init system within each Container Machine. This enables comprehensive testing of complex, multi-service applications that rely on persistent services and process supervision. For instance, you can run a PostgreSQL database as an actual service alongside a web server, configuring them precisely as they would operate on a production Linux server. This capability ensures more accurate local testing for intricate deployments, significantly reducing discrepancies between development and production environments on Apple Silicon. Developers gain a true-to-production testing ground directly on their Mac.
Performance Showdown: Apple vs. OrbStack
Benchmarks reveal Apple Container Machines deliver robust performance, frequently surpassing Docker Desktop and often matching OrbStack in raw CPU and memory throughput. Initial tests show Apple's micro-VM architecture holds its own against established players, a strong debut for the first-party solution.
OrbStack maintains a critical advantage in specific areas, however. Its superior filesystem performance and small-file I/O speeds remain unmatched by Container Machines. For development workflows heavily reliant on rapid file operations, OrbStack still offers a tangible edge.
A significant drawback for Apple's solution lies in resource management. Container Machines reserve a substantial portion of system RAM—half of your Mac’s memory by default—and critically, never release it. OrbStack’s dynamic memory allocation proves far more efficient, adapting to actual workload demands.
This static allocation can severely impact overall system responsiveness, especially on Macs with 16GB RAM or less. While Apple's offering shows immense promise, this memory behavior is a clear area for improvement. For more architectural details, refer to Discover container machines - WWDC26 - Videos - Apple Developer.
Enjoying this? Get one like it in your inbox each morning.
one email a day · unsubscribe in two clicks · no third-party tracking
The Catches: Should You Switch Today?
Apple's Container Machines, while performant, arrive with notable limitations. Developers will immediately miss GPU passthrough and USB passthrough, which are critical for hardware-intensive tasks or specific peripheral interactions. Running Linux GUI applications also proves challenging, restricting its utility for many desktop-focused development workflows.
Convenience comes at a cost, particularly with the default home directory mount. This read-write access exposes all your Mac files—including sensitive SSH keys and cloud credentials—to any process within the Linux VM. This significant security trade-off demands careful consideration, as it offers far less isolation than expected from a containerized environment.
Ultimately, Apple's Container Machines are a powerful and promising first-party solution, especially for those committed to the Apple ecosystem and its tight integration. However, for most professional developers today, polished alternatives like OrbStack remain a safer, more feature-rich choice. OrbStack provides superior isolation and broader feature sets, making it the current frontrunner for demanding Linux development on macOS.
Frequently Asked Questions
What are Apple Container Machines?
Apple Container Machines are a new macOS feature that provides lightweight, persistent Linux virtual environments, similar to the Windows Subsystem for Linux (WSL). They are built on Apple's native Container project and optimized for Apple Silicon.
How do Container Machines differ from Docker Desktop?
The main difference is architecture. Container Machines run each container in its own isolated, lightweight VM using Apple's Virtualization Framework. Docker Desktop typically runs multiple containers within a single, shared Linux VM.
Can I run my existing Docker images with Apple Container Machines?
Yes. Apple's container tool works with any standard OCI (Open Container Initiative) compatible image. You can build an image from a Dockerfile and use it to create a Container Machine.
What are the main limitations of Apple Container Machines right now?
Current limitations include no GPU or USB passthrough, inefficient memory management (it doesn't release unused RAM back to macOS), and a significant security risk due to the default read-write access to the entire user home directory.