> When it gets too out of hand, people will paper it over with a new, simpler abstraction layer, and the process starts again, only with a layer of garbage spaghetti underneath. I'm pretty happy that there are S3 compatible stores that you can host yourself, that aren't insanely complex. MinIO: https://min.io/ SeaweedFS: https://github.com/seaweedfs/seaweedfs Of course, many will prefer hosted/managed solutions... - Source: Hacker News / 10 days ago

What distributed file system would you use for a greenfield homelab project today? Requirements / desires: * Reliable * Performant * Easy to setup and operate Some options: SeaweedFS - https://github.com/seaweedfs/seaweedfs 289 hits: https://hn.algolia.com/?dateRange=all&page=0&prefix=true&query=seaweedfs&sort=byPopularity&type=all JuiceFS - https://github.com/juicedata/juicefs 2047 hits:... - Source: Hacker News / 22 days ago

> Theoretically they could swap with minio but last time we used it it was not a drop-in replacement yet. Depends on whether AGPL v3 works for you or not (or whether you decide to pay them), I guess: https://min.io/pricing I've actually been looking for more open alternatives, but haven't found much. Zenko CloudServer seemed to be somewhat promising, but doesn't seem to be managed very actively:... - Source: Hacker News / 7 months ago

Wireguard + GUI: https://github.com/wg-easy/wg-easy Backups of mail accounts: https://www.offlineimap.org Cloud storage for phones: http://nextcloud.com Mirroring podcasts locally: https://github.com/akhilrex/podgrab My own matrix instance: https://matrix-org.github.io/dendrite/ Backups: https://restic.net Media Management: https://jellyfin.org Relay only tor help: https://www.torproject.org S3 compatible storage:... - Source: Hacker News / 8 months ago

JuiceFS is mostly POSIX compatible, but there are important caveats to that like no ACL, copying files changes their mtime (which impacts backup tools), has "close-to-open" consistency (which makes it dangerous for log appenders). Choosing an appropriate solution in this space still depends on what you need to do with the storage, and some options are MooseFS https://github.com/moosefs/moosefs, Curve... - Source: Hacker News / about 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

Multiple container runtimes are supported, like conatinerd, cri-o, or other CRI compliant runtimes. - Source: dev.to / 6 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