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... - Source: dev.to / 4 months ago

Multiple container runtimes are supported, like conatinerd, cri-o, or other CRI compliant runtimes. - Source: dev.to / 5 months ago

Install container runtime on all nodes. We will use cri-o. - Source: dev.to / 6 months ago

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. - Source: dev.to / 10 months ago

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. - Source: dev.to / 12 months ago

I have heard of slim.ai, there core tool is open source Https://github.com/docker-slim/docker-slim. Source: almost 2 years ago

* We have a lightweight engineering process based on trust, self-alignment and visibility. Email me at cto@slim.ai if you'd like to learn more. P.S. Take a look at DockerSlim ( https://github.com/docker-slim/docker-slim ) if you are interested in working on the open source project that powers our SaaS. - Source: Hacker News / about 2 years ago

In last weeks blog I talked about what my plan was for release 2.9. My main areas of concern was finishing the migration to make use of the images stored in our Docker registry. The other area I was planning on taking on was to slim down those images in the registry by using Docker-Slim. - Source: dev.to / about 2 years ago

Or you can save your time micromanaging your Dockerfile and just use docker-slim. Source: about 2 years ago

In my experience docker-slim[0] is the way to go for creating minimal and secure Docker images. I wasted a lot of time in the past trying to ship with Alpine base images and statically compiling complicated software. All the performance, compatibility, package availability headaches this brings is not worth it when docker-slim does a better job of removing OS from your images while letting you use any base image... - Source: Hacker News / about 2 years ago