Apple just open-sourced Container Machines, a lightweight Linux virtualization solution for macOS—and if you're the developer behind OrbStack or similar tools, you're probably having flashbacks to every other time Apple "Sherlock-ed" a third-party solution.
Container Machines provides what Apple calls "a highly integrated Linux environment that works seamlessly on your Mac." Each machine runs in its own minimal VM using Apple's Virtualization.framework, offering three key advantages: security through full VM isolation, privacy via selective data mounting, and performance with less memory overhead than traditional VMs.
The implementation is clever. Your Mac home directory automatically maps into the container at <code>/Users/<username></code>, eliminating the need to copy files between systems. The container provisions a user account matching your host username—no default root access. And unlike ephemeral application containers, these machines maintain persistent state across sessions.
Technically, it's impressive. Any Linux image containing <code>/sbin/init</code> works as a valid container machine image. You can run actual init systems, enabling commands like <code>systemctl start postgresql</code>. You can spin up multiple environments running different distributions (Alpine, Ubuntu, Debian) while sharing the same home directory. It uses the Kata container kernel by default and virtiofs for filesystem mounting.
But here's where it gets interesting: OrbStack already does much of this, and arguably does some parts better. The OrbStack developer quickly pointed out that "dynamic memory management—releasing unused RAM back to macOS—is a distinguishing feature unavailable in Apple's offering." Apple's version allocates memory but can't release it, and there's no USB passthrough (though macOS 27 adds this capability).
The developer community's reaction was predictable. "Apple Sherlock-ing OrbStack. Classic Apple move," noted one commenter. And they're not wrong—this is Apple's pattern. See a clever third-party solution gaining traction? Build it into the OS.
Should we be cynical about this? Maybe not entirely. Apple's version is open source, which means the community can contribute and improve it. It'll be deeply integrated with macOS in ways third-party tools can't match. And competition pushes everyone to build better tools.
But it's also fair to acknowledge that building developer tools is risky when Apple might decide your use case is important enough to absorb into the platform. OrbStack still has advantages—better memory management, more polish, features Apple hasn't implemented. Whether those are enough to maintain a business when Apple offers a "good enough" free alternative? That's the question every Mac developer eventually faces.
The technology is impressive. The question is whether we want a platform where building successful developer tools means waiting for Apple to inevitably compete with you.
