hyperkit VS bravetools

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.

We're using Multipass + Bravetools (https://github.com/bravetools/bravetools) / Docker to build system/application containers.

I believe multipass uses SSHFS (https://discourse.ubuntu.com/t/how-to-improve-mounts-perform...) to mount filesystems between the host and the VM. Performance has been excellent.

We've been working on a docker-compose-like system for LXD - https://github.com/bravetools/bravetools and have been shipping products with its declarative yaml configuration. The combination of declarative approach with the benefits of LXD has worked really well.

Could you raise this asn an issue on our github page? Would be easier to support as others could chip in https://github.com/bravetools/bravetools/issues

Because some containers require a bespoke configuration, we’re using bravetools (https://github.com/bravetools/bravetools) to automate custom image builds and deployment.

Code: https://github.com/bravetools/bravetools Docs: https://bravetools.github.io/bravetools/