Based on our record, containerd should be more popular than ROOK. It has been mentiond 45 times since March 2021. We are tracking product recommendations and mentions on various public social media platforms and blogs. They can help you identify which product is more popular and what people think of it.
I have some experience with Ceph, both for work, and with homelab-y stuff. First, bear in mind that Ceph is a distributed storage system - so the idea is that you will have multiple nodes. For learning, you can definitely virtualise it all on a single box - but you'll have a better time with discrete physical machines. Also, Ceph does prefer physical access to disks (similar to ZFS). And you do need decent... - Source: Hacker News / 4 months ago
Another option is to leverage a Kubernetes-native distributed storage solution such as Rook Ceph as the storage backend for stateful components running on Kubernetes. This has the benefit of simplifying application configuration while addressing business requirements for data backup and recovery such as the ability to take volume snapshots at a regular interval and perform application-level data recovery in case... - Source: dev.to / 5 months ago
This is beyond your question but might help someone else: I switch from docker-compose to kubernetes for my home lab a while ago. The storage solution I've settled on is Rook. It was a bit of up-front work learning how to get it up but now that it's done my storage is automatically managed by Ceph. I can swap out drives and Ceph basically takes care of everything itself. Source: 11 months ago
The stumbling point I am at is I want to use rook.io(Ceph) as my storage solution for the cluster. The Ceph prerequisites are one of the following:. Source: about 1 year ago
Storage: Favor any distributed storage you know to start with for Persistent Volumes: Ceph maybe via rook.io, Longhorn if you go rancher etc. Source: over 1 year ago
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
Container Engine: A runtime that executes and manages containers. Docker and containerd are popular container engines. - 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
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:. - Source: dev.to / 9 months ago
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/. Source: 12 months ago
Minio - Minio is an open-source minimal cloud storage server.
rkt - App Container runtime
Ceph - Ceph is a distributed object store and file system designed to provide excellent performance...
CRI-O - Lightweight Container Runtime for Kubernetes
Openstack Swift - Application and Data, Data Stores, and Cloud Storage
GlusterFS - GlusterFS is a scale-out network-attached storage file system.