SSVM
cri-tools
Our great sponsors
| SSVM | cri-tools | |
|---|---|---|
| 50 | 7 | |
| 7,952 | 1,551 | |
| 3.3% | 1.4% | |
| 9.7 | 9.2 | |
| about 9 hours 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-tools
-
Migrating from dockershim to containerd
Installing crictl (https://github.com/kubernetes-sigs/cri-tools/blob/master/docs/crictl.md) was helpful, as well as journalctl -u containerd.
- kubectl get nodes -o wide shows containerd runtime, but sudo ctr containers list doesn't return any containers on host
-
Debugging containerd, A "new" container runtime means new debugging techniques are required
crictl: Uses the CRI interface to fetch data about containers, agnostic of CRIs. Maintained by Kubernetes at https://github.com/kubernetes-sigs/cri-tools
-
Quick question: Can you run crictl commands from within a running container?
FROM alpine:latest RUN wget -O - https://github.com/kubernetes-sigs/cri-tools/releases/download/v1.23.0/crictl-v1.23.0-linux-amd64.tar.gz | gunzip | tar xvf - && mv crictl /usr/bin
-
k8s-the-hard-way
# wget https://github.com/kubernetes-sigs/cri-tools/releases/download/v1.21.0/crictl-v1.21.0-linux-amd64.tar.gz \ https://github.com/opencontainers/runc/releases/download/v1.0.0-rc93/runc.amd64 \ https://github.com/containernetworking/plugins/releases/download/v0.9.1/cni-plugins-linux-amd64-v0.9.1.tgz \ https://github.com/containerd/containerd/releases/download/v1.4.4/containerd-1.4.4-linux-amd64.tar.gz \ https://storage.googleapis.com/kubernetes-release/release/v1.21.0/bin/linux/amd64/kubectl \ https://storage.googleapis.com/kubernetes-release/release/v1.21.0/bin/linux/amd64/kube-proxy \ https://storage.googleapis.com/kubernetes-release/release/v1.21.0/bin/linux/amd64/kubelet
-
A Window into Docker, minikube, and containerd
We are in the endgame now. I promise. From the README, crictl provides a CLI for CRI-compatible container runtimes. The following snippet performs the following:
-
😎 Manage WebAssembly Apps in WasmEdge Using Docker Tools
Also make sure that you have cri-o, crictl, containernetworking-plugins, and buildah or docker installed.
What are some alternatives?
wasmer - 🚀 The leading Wasm Runtime supporting WASIX, WASI and Emscripten
node-feature-discovery - Node feature discovery for Kubernetes
wasmtime - A fast and secure runtime for WebAssembly
cni - Container Network Interface - networking for Linux containers
aws-lambda-wasm-runtime - A template project for building high-performance, portable, and safe serverless functions in AWS Lambda.
cfssl - CFSSL: Cloudflare's PKI and TLS toolkit
WAVM - WebAssembly Virtual Machine
runc - CLI tool for spawning and running containers according to the OCI specification
dapr-wasm - A template project to demonstrate how to run WebAssembly functions as sidecar microservices in dapr
rustwasmc - Tool for building Rust functions for Node.js. Combine the performance of Rust, safety and portability of WebAssembly, and ease of use of JavaScript.
WasmEdge-go - The GO language SDK and API for WasmEdge
wasm-learning - Building Rust functions for Node.js to take advantage of Rust's performance, WebAssembly's security and portability, and JavaScript's ease-of-use. Demo code and recipes.