hyperkit

Will not work with Docker on Mac: https://github.com/moby/hyperkit/issues/127

Semgrep is the most famous one I could think of offhand: https://github.com/returntocorp/semgrep/blob/v1.2.1/Dockerfi... Hyperkit from the docker/moby folks is another: https://github.com/moby/hyperkit/tree/v0.20210107 And while niche, Coq is not exactly unheard of: https://github.com/coq/coq/tree/V8.16.1 If you weren't already aware, GitHub supports searching by the repo's more prominent language: https://github.com/search?o=desc&q=language%3Aocaml&s=stars&...

> I don't use a VM for Docker. Yes you are. https://github.com/moby/hyperkit (Or maybe you mean a non-Docker For Mac VM)

Docker is using hyperkit [1], an xhyve fork that's still actively developed. [1] https://github.com/moby/hyperkit

If easy is the goal, have a look at Multipass (https://multipass.run/docs/installing-on-macos), which uses hyperkit as the backend (https://github.com/moby/hyperkit)

I believe Docker For Mac uses Hyperkit now, an offshoot of xhyve. https://github.com/moby/hyperkit

Docker has their own xhyve derivative called hyperkit. Nested VMs are not supported https://github.com/moby/hyperkit/issues/127

It uses Hyperkit: https://github.com/moby/hyperkit

macOS has a native hypervisor framework, Docker and xhyve uses it. https://developer.apple.com/documentation/hypervisor https://github.com/moby/hyperkit

Indeed, it's called HyperKit[0][1], and it's based straight off xhyve[2]. Also, there's docker-machine-driver-xhyve for people that prefer using docker-machine (like I do) instead of DfM. [0]: https://github.com/moby/hyperkit [1]: https://blog.docker.com/2016/05/docker-unikernels-open-sourc... [2]: https://github.com/moby/hyperkit/tree/master/src/

For those interested, some of the underlying libraries that make up Docker for Mac (and, I think, Windows) are written in OCaml (or have components written in OCaml): VPNKit[0], DataKit[1] and HyperKit[2] (qcow2 support is implemented in OCaml). 0: https://github.com/moby/vpnkit 1: https://github.com/moby/datakit 2: https://github.com/moby/hyperkit

WSL is really interesting. I switched to the Mac in 2006 but I’ve never really used the fact it’s built on Unix much because it’s so different and frankly outdated comparede to the Linux systems I work on. When I want to do ‘Unixy’ stuff at home I run a Linux VM in VirtualBox. But WSL seems to offer the best of both worlds – a solid mature desktop environment with plenty of well supported professional level apps and an approaching first class Linux environment baked right in. I’m still very happy on the Mac and would miss a lot of Mac specific features and applications, but this is the first thing to happen in Windows Land that’s made me even think of the possibility of wanting to run Windows at home for over 10 years. Edit: What would be the nearest thing to WSL on a Mac? VirtualBox is a bit heavy-weight. Maybe something based on Hyperki

Docker has taken the direction of a loose collection of tools tied together by an integrated interface. So you have the choice of using the platform as a whole, or standing up your choice of individual components on their own, without any dependency on Docker. Based on your comment, you're probably not the target audience for the platform. I recommend checking out some of the components to see if they meet your criteria of simplicity. A few examples: https://runc.io https://containerd.tools https://github.com/docker/swarmkit https://github.com/docker/notary https://github.com/docker/infrakit https://github.com/docker/hyperkit We are continuing the work of carving out more and more usable components from the platform.

Mac OS X has an hypervisor framework, which is also used by Docker https://github.com/docker/hyperkit https://developer.apple.com/reference/hypervisor Also there is App Sandbox for writing safer applications, but it requires programming explicitly against it. https://developer.apple.com/library/content/documentation/Se...

We'll probably use AHCI since hyperkit https://github.com/docker/hyperkit (the Mac hypervisor based on xhyve based on bhyve) lacks a virtio-scsi implementation at the moment. When the VM sends a TRIM ("these blocks aren't used any more, you can free them") we need to make use of this on the host. On Linux/BSD you could tell the host OS that the blocks aren't needed in the file using something like FALLOC_FL_PUNCH_HOLE and the kernel would take care of it e.g. by send TRIMs to the real storage device or shuffling filesystem metadata around. Unfortunately the Mac filesystems in common use don't support this so we'll need to manage this ourselves, e.g. by moving blocks from the end of the file into the middle and shrinking the file.