I have to admit that in the container world I can't keep up with the different standards, what they each cover, and the different implementations of them. I think a non-docker K8s is already possible, this just reuses that stack while reimplementing part of it in order to make the cli more like the docker cli? Maybe despite the description this is actually intended to be used outside of K8s?
Two months ago, I did not know what Kubernetes was exactly, or how containerization worked. Some of the team from the Rancher slack answered a few basic questions I had, and I attended a 2-hour Kubernetes webinar by them, which was also cool. Now I have a suite of half a dozen services running on a cloud k8s cluster in production.
Overall these guys are rockstars, I cannot wait until I can use k3s as a drop-in replacement for Microk8s for local dev (currently has a few bugs).
Holistic Rancher stack, k3s + k3c locally, bootstrap a cloud cluster with Rancher, manage deployments with Rio
rkt feels actively hostile and I won't be using it. If I work for someone who is, I can find a different part of the stack to inhabit until they change their minds.
Today MacOS users need to revert back to vagrant or to adopt a newer VM-management tool like https://multipass.run and create a full Linux VM to enjoy tooling k3c from a Mac.
I also ran into this developing a containerd backend for OpenFaaS called faasd - https://github.com/alexellis/faasd
We need an experience like Docker Desktop, but for containerd, or for Linux in general on MacOS. Any ideas here Darren?