https://developer.apple.com/documentation/hypervisor https://github.com/moby/hyperkit
Further, there's no decent solution for shipping a macOS container image to run in a VM. Linux, yes, Mac, no.
Finally, good luck getting your virtualized macOS app to interact reasonably with your main OS (no drag and drop, no OpenGL, etc.).
I would rather chroot.
IIRC the Docker implementation for OS X runs a tiny, carefully-configured Linux VM transparently in the background. This isn't that dissimilar from the Windows Subsystem for Linux from a user standpoint.
I've done plenty of Docker work on OS X; the only real weirdness is that you're running Linux in the containers and OS X outside. Eventually, though, before switching completely to a native Linux desktop, I moved deeper into the containers and would barely ever see the OS X command prompt any more.
Does anyone actually use Docker on Mac?
Xhyve is more of a proof-of-concept than a production-ready tool.
What? We use it at work every day for local development, and my previous employer did as well. It has issues, definitely, but they have more to do with Docker than with xhyve.
I use it extensively. It is a desktop product however; it you aren't expected to put a swarm of MacBook pros into production.
Calling it “not serious” is quite wrong.
Sure, for development tasks.
All the interesting container stuff is on other platforms.
It might be out of fear, maybe because apple doesn't want macos to be virtualized.
It would be really nice to have say the current xcode in one container and a dev xcode in another. It would be nice to farm work out to a lot of machines.
or a dockerfile like: FROM macos:10.14
RUN installer xcode... RUN xcode-build myproject
Given that Apple is (or at least was) one of the biggest users of Mesos in the world and have invited me to interview specifically on the back of the operationalization of containers, I'm guessing that the staggeringly bright programmers they've got probably understand containers.
Just a little hunch, you know?
Maybe it's another "you're not the target market" kind of thing.
The point I'm getting at is that folks on other platforms have lots and lots of options and apple doesn't provide any.
The macOS EULA explicitly allows macOS to be virtualized if you do it on a Mac running macOS.
> It would be really nice to have say the current xcode in one container and a dev xcode in another.
This is the entire point behind xcode-select. I currently have Xcode-beta and Xcode on side-by-side on my machine, and they pretty much coexist.
- I think xcode-select just modifies a .plist.
They do offer a set of "primitives" for virtualization, which can be hooked into by third-party solutions like Docker if they want to do so.