Fedora-Remix-for-WSL VS cri-o

At the risk of being downvoted to hell, but to offer a different perspective, my answer is, that my favorite DE for Linux (not only Fedora) is... Windows with WSL(g). I'm a huge Fedora fan, have installed it bare-metal, but use fedoraremix WSL distro almost exclusively. The problem with that solution is that it requires an absurdly huge amount of memory to work comfortably, so I admit, that it is not a good solution for any system with less than 32GB of RAM.

You could download the msix bundle for fedora remix from Github or using winget: winget install --id whitewaterfoundry.fedora-remix-for-wsl

BTW. I'm not using Ubuntu WSL, and I'm on fedoraremix instead - you can install it for free from https://github.com/WhitewaterFoundry/Fedora-Remix-for-WSL/releases. As of now it installs Fedora 35, but you can upgrade it to 36 and there you have podman 4.2.0 available for install. Maybe it would solve some of your issues?

[2]: https://github.com/WhitewaterFoundry/Fedora-Remix-for-WSL

Disclaimer. I am not using Windows to test above solutions anymore. More than a year ago I used [2] but from a casual look maybe [1] is better now.

Lol, you could have sideloaded it for free.

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.

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

Install container runtime on all nodes. We will use cri-o.

Container Runtime Interface (CRI) is one of the important parts of the Kubernetes cluster. It is a plugin interface allowing kubelet to use different container runtimes. And recently CRI-O container runtime has been announced as a CNCF Graduated project. I thought of writing a blog on CRI-O and how to set up a single-node Kubernetes cluster with Kubeadm and CRI-O.

CRI-O: This is an open-source container runtime designed for use with Kubernetes. It is a lightweight and stable environment for containers. It also complies with the Kubernetes Container Runtime Interface (CRI), making it easy to integrate with Kubernetes.

With CRI-O I believe you can configure registry mirror locations…. Similar to this: https://github.com/cri-o/cri-o/issues/4941

Alternatives like Podman and CRI-O continue to gain traction and may replace Docker in various places. For example, Kubernetes used to use Docker, then moved to containerd, and now also support CRI-O. Generally speaking, the core features of "Docker" are such a commodity now that no one was the wiser when Kubernetes stopped using it.

will the site be available for the CKA exam? https://github.com/cri-o/cri-o/blob/main/install.md

The CRI-O container engine provides a stable, more secure, and performant platform for running Open Container Initiative (OCI) compatible runtimes. CRI-Os purpose is to be the container engine that implements the Kubernetes Container Runtime Interface (CRI) for OpenShift Container Platform and Kubernetes, replacing the Docker service. Source