Docker Hyperkit Mac OS Was Different
Docker Hyperkit Mac Edge Build

For example, in order for a Container to readwrite from your Host OS hard drive, it has to.

For example, in order for a VM to readwrite from your Host OS hard drive, it has to.

All that synchronizing work between these layers is not trivial.

While it is true that Docker on Linux is the architecture as intended (and therefore is the best experience), simply switching is not tenable for most folks.

At the very least, the jet plane taking off might only happen every once in a while versus all the time.

Docker Hyperkit Mac Edge Build

You wont have to worry about the details though, as they package it as part of the Docker for Mac Edge build.

It is, in effect, another abstraction layer to speed up the process.

As it proved out its utility, it was eventually ported to macOS and Windows.

This unfortunately results in these low-level inefficiencies that we otherwise take for granted.

Docker Hyperkit Mac OS Was Different

I knew that Docker for Mac OS was different and running inside a VM, but not with such details.

We have a pretty IO heavy setup with our front-end (i.e.

Checking my Activity Monitor right now, at idle, my docker.hyperkit on my MBP sits at 40.and thats with help from docker-sync.

If indeed the case generally, Docker devs should suggest such a solution, rather than providing a substandard VM of their own for MacOS.

Im hearing these reports after learning of Doki malware and Im losing confidence in the product.

Or should I say Im losing faith in the organization behind the product.

Docker for Mac will be at the mercy of the macOS Hyperkit.

Docker For Mac Hyperkit