wasi-sql
containerd-wasm-shims
wasi-sql | containerd-wasm-shims | |
---|---|---|
1 | 4 | |
20 | 293 | |
- | 3.4% | |
3.9 | 8.1 | |
3 months ago | about 2 months ago | |
Rust | ||
- | 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.
wasi-sql
-
Spin 1.0 — The Developer Tool for Serverless WebAssembly
We are excited to contribute back to Wasmtime and the component model, as well as to new projects and proposals emerging in this space (such as new Wasm proposals, like WASI Preview 2, wasi-keyvalue, wasi-sql or wasi-cloud).
containerd-wasm-shims
-
Spin 1.0 — The Developer Tool for Serverless WebAssembly
Besides deploying the application locally and deploying to Fermyon Cloud, you can also deploy your Spin application to Kubernetes using the new Containerd integration for Spin.
-
Why did the Krustlet project die?
Yeah, runtimeClass lets you specify which CRI plugin you want based on what you have available. Here's an example from the containerd documentation - you could have one node that can run containers under standard runc, gvisor, kata containers, or WASM. Without runtimeClass, you'd need either some form of custom solution or four differently configured nodes to run those different runtimes. That's how krustlet did it - you'd have kubelet/containerd nodes and krustlet/wasm nodes, and could only run the appropriate workload on each node type.
-
New Docker Desktop: Run WASM Applications Alongside Linux Containers in Docker
You can absolutely install the wasm shim without Desktop. (They won't tell you that because Desktop is a revenue stream for Mirantis.)
In your VM or WSL instance that's running Docker, get the shim from here: https://github.com/deislabs/containerd-wasm-shims (You might need to build it yourself)
Then specify the --runtime and --platform arguments like instructed in the doc, but with a slight modification:
--runtime=containerd-wasm-shim=/path/to/containerd/wasm/shim
This works because the container runtime is simply a Go binary, and Go binaries are completely self-contained.
What are some alternatives?
spin-planetscale-f1
krustlet - Kubernetes Rust Kubelet
spin-js-sdk - https://developer.fermyon.com/spin/javascript-components
spin-plugin-k8s - A Kubernetes Plugin for Fermyon Spin
spin-fileserver - A static file server implemented as a Spin component
preview2-prototyping - Polyfill adapter for preview1-using wasm modules to call preview2 functions.
runwasi - Implementation for runs wasm workloads in Wasmedge
Podman Desktop - Podman Desktop - A graphical tool for developing on containers and Kubernetes
crun - A fast and lightweight fully featured OCI runtime and C library for running containers
colima - Container runtimes on macOS (and Linux) with minimal setup