SSVM
cri-o
Our great sponsors
SSVM | cri-o | |
---|---|---|
50 | 33 | |
7,932 | 5,013 | |
3.3% | 1.1% | |
9.8 | 9.7 | |
5 days ago | 7 days ago | |
C++ | Go | |
Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
SSVM
- A WASM runtime for running LLMs locally
-
Time-series data ingestion from Rust WebAssembly application, leveraging GreptimeDB and WasmEdge
WasmEdge GitHub address: https://github.com/WasmEdge/WasmEdge.
-
Orca-2-13B Runs Directly on Rust+WASM – No Python/C++ Hassles
I see that they recently changed the intro of WasmEdge on Github [1] to " WasmEdge is the easiest and fastest way to run LLMs on your own devices. "
Since it's a wasm runtime capable of many things I find bizarre that they now start describing it with a ultra-specific use case
- [1] https://github.com/WasmEdge/WasmEdge
-
Run LLMs on my own Mac fast and efficient Only 2 MBs
Mmm…
The wasm-nn that this relies on (https://github.com/WebAssembly/wasi-nn) is a proposal that relies of arbitrary plugin backends sending arbitrarily chunks to some vendor implementation. The api is literally like set input, compute, set output.
…and that is totally non portable.
The reason this works, is because it’s relying on the abstraction already implemented in llama.cpp that allows it to take a gguf model and map it to multiple hardware targets,which you can see has been lifted here: https://github.com/WasmEdge/WasmEdge/tree/master/plugins/was...
So..
> Developers can refer to this project to write their machine learning application in a high-level language using the bindings, compile it to WebAssembly, and run it with a WebAssembly runtime that supports the wasi-nn proposal, such as WasmEdge.
Is total rubbish; no, you can’t.
This isn’t portable.
It’s not sandboxed.
If you have a wasm binary you might be able to run it if the version of the runtime you’re using happens to implement the specific ggml backend you need, which it probably doesn’t… because there’s literally no requirement for it to do so.
There’s a lot of “so portable” talk in this article which really seems misplaced.
- Security Slam 2023: Contribute to WasmEdge and Elevate Open Source Security
-
Requiem for a Stringref
WasmEdge isn't there yet: https://github.com/WasmEdge/WasmEdge/issues/1122#issuecommen...
- Should You Be Scared of Unix Signals?
- WasmEdge 0.13.0: Unified CLI, ARM Support and Migrating Extensions to Plugins
-
ChatGPT-powered code review bot to boost your PR merge. Deploy in 5 mins
Example 1: Analyze the content and risks of each commit in the PR. Then make a summary. https://github.com/WasmEdge/WasmEdge/pull/2394#issuecomment-...
-
Cloud, Why So Difficult?
There has also been a few "cloud-native" runtimes based on WASM, like WasmEdge but there's a few others (can't remember their names!)...
cri-o
-
The Road To Kubernetes: How Older Technologies Add Up
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.
-
Complexity by Simplicity - A Deep Dive Into Kubernetes Components
Multiple container runtimes are supported, like conatinerd, cri-o, or other CRI compliant runtimes.
-
Kubernetes Cluster Setup Using Kubeadm on AWS
Install container runtime on all nodes. We will use cri-o.
-
Creating Kubernetes Cluster With 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.
- 32“ E Ink screen that displays daily newspapers on your wall
-
Understanding Docker Architecture: A Beginner's Guide to How Docker Works
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.
-
How are they doing it?
With CRI-O I believe you can configure registry mirror locations…. Similar to this: https://github.com/cri-o/cri-o/issues/4941
-
Docker is deleting Open Source organisations - what you need to know
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.
-
kubeadm init error: CRI v1 runtime API is not implemented
will the site be available for the CKA exam? https://github.com/cri-o/cri-o/blob/main/install.md
-
Container Deep Dive 2: Container Engines
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
What are some alternatives?
wasmer - 🚀 The leading Wasm Runtime supporting WASIX, WASI and Emscripten
containerd - An open and reliable container runtime
wasmtime - A fast and secure runtime for WebAssembly
crun - A fast and lightweight fully featured OCI runtime and C library for running containers
aws-lambda-wasm-runtime - A template project for building high-performance, portable, and safe serverless functions in AWS Lambda.
k3s - Lightweight Kubernetes
WAVM - WebAssembly Virtual Machine
minikube - Run Kubernetes locally
dapr-wasm - A template project to demonstrate how to run WebAssembly functions as sidecar microservices in dapr
cri-dockerd - dockerd as a compliant Container Runtime Interface for Kubernetes
WasmEdge-go - The GO language SDK and API for WasmEdge
kaniko - Build Container Images In Kubernetes