hyperkit VS containerd

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.

Containerd and nerdctl

Kubernetes on the backend used to utilize docker for much of its container runtime solutions. One of the modular features of Kubernetes is the ability to utilize a Container Runtime Interface or CRI. The problem was that Docker didn't really meet the spec properly and they had to maintain a shim to translate properly. Instead users could utilize the popular containerd or cri-o runtimes. These follow the Open Container Initiative or OCI's guidelines on container formats.

Container Engine: A runtime that executes and manages containers. Docker and containerd are popular container engines.

Multiple container runtimes are supported, like conatinerd, cri-o, or other CRI compliant runtimes.

This is a failed attempt to upstream part of containerd changes: https://github.com/containerd/containerd/pull/8789

Other part of containerd changes waits for gods-know-what: https://github.com/containerd/containerd/pull/9054

But I haven't gave up yet.

containerd is required by kubernetes to handle containers on its behalf. A big thanks to the HostAfrica blog for the information on setting containerd up for debain. So the containerd install will need to happen on both the WSL2 instance and the Raspberry Pis. For WSL2 you can just install containerd directly:

The context deadline exceeded: unknown is also in containerd, and is a known problem.

Get:1 https://download.docker.com/linux/ubuntu focal/stable amd64 containerd.io amd64 1.6.21-1 [28.3 MB]

Docker Desktop adds a bunch of stuff to simplify local development and that’s why it has a larger memory footprint. You don’t use that when deploying but something like https://containerd.io/.