hyperkit VS lima

The author uses a Mac and uses Docker Desktop or colima x Docker CLI to realize a Docker development environment. Dcoker Desktop uses an internal HyperKit (macOS hypervisor) to launch a Linux VM and run dockerd in it. Docker Desktop is based on Lima, and it generates Lima configuration files, and it is used to run Linux.

Sorry, I was misinformed. It seems MacOS still does use a tool called hyperkit to run a (presumably linux) VM as a backend for docker. I thought it was using something similar to jails.

You might try using HyperKit as the hypervisor with Kubernetes. It uses Apple's own hypervisor. Minikube, or rather docker, supports it. I would go with minicube as you can start and stop it as needed with ease.

I've been reading many forum posts: moby/hyperkit#149 docker/for-mac#900

What’s the magic behind docker working on macOS?. The answer is virtualization accomplished by the moby/hyperkit hypervisor (AFAIK), a toolkit for embedding hypervisor capabilities in your application, which means that dockerd works in a VM virtualized by the hyperkit. Why I’m telling you this is once you decide to work with containerd on your macOS environment to discover capabilities and more adapt to it because we assume you use containerd in your Kubernetes environment as a default container runtime, you had to have the same virtualization technology under the hood to let containerd working on macOS. Also, you need to have some client tooling to interact with containerd by keeping simplicity and usability in mind.

Docker on Mac is based on Hyperkit which is a lightweight VM. https://github.com/moby/hyperkit Crostini is running in a full KVM instance. You challenged me about the Termina shell. Type it in and see if I'm right. No need to debate this anymore when you can verify for yourself.

Docker Desktop doesn't use virtualbox behind the scenes. It uses hyperkit.

You can run a virtual machine (e.g. lima) from inside a nix-shell, exactly as you would do with a regular shell.

for others similarly curious, here's an example of the thing: https://github.com/noop-inc/template-java-spring-boot/blob/m...

they seem to be using the excellent lima <https://github.com/lima-vm/lima#readme> for booting on macOS; I run colima for its containerd and k8s support but strongly recommend both projects $(brew install lima colima)

Lima is what I use as well. It's quick and easy to just fire up a VM with default settings, but also very easy to configure with different file sharing options, port forwarding, different linux distributions, etc. (their examples are also pretty good IMO [1]).

In particular I use it to run an amd64 VM, which I need to run a stubborn service for work that doesn't run on arm CPUs.

[1] https://github.com/lima-vm/lima/tree/master/examples

Lima (1) is a project that packages Linux distros for MacOS and executes them via qemu in the backend. Maybe you could solve your problem by launching one of their vms and inspecting the command line it generates. You might find an option you were missing.

(1) https://github.com/lima-vm/lima

If you wish to delve into all the configuration possibilities for Lima VM, you can visit this resource.

I'd say Lima and Colima should be enough for most use cases:

https://lima-vm.io/

https://github.com/abiosoft/colima

Github: https://github.com/lima-vm/lima

Lima wraps QEMU in a simple CLI, with neat features for container users, such as filesystem sharing and automatic localhost port forwarding, as well as DNS and proxy propagation for enterprise networks. Rancher Desktop wraps Lima with k3s integration and GUI.

Talks: https://github.com/lima-vm/lima/blob/master/docs/talks.md