CRI-O's WASM Adventure: Challenges, Strategies, and What Lies Ahead
summary
CRI-O adds practical WASM support by running WASM OCI images with crun-wasm (using wasmEdge in demos) and a new config field platformRuntimeParts to map architectures to runtimes; runc lacks WASM support and OCI image annotations are awkward to pass, so assigning the correct runtime at pod creation is a core challenge. Demo runs a WASI HTTP server and an Llama model from a mounted volume (it works but is clumsy). Future plans: run runtimes directly in CRI-O and load WASM plugins in-CRIO to replace external NRI daemons.
AI-written summary · about
chapters (10)
- 0:00CRI-O and WASM intro
- 1:04WASM in container space
- 2:47WASM benefits with CRI-O
- 6:42WASM integration challenges
- 8:52Live WASM workload demo
- 12:24Future WASM plans
- 21:22Optimizing WASM runtime
- 24:30NRI for WASM plugins
- 28:01CRI-O’s WASM vision
- 33:47Q&A
related talks
31mJamming with CRI-O & crun: Facilitating the Convergence of AI, WASM, and Kubernetes
35mContain Yourself: Wasm and the OCI Spec
10mEverything You Wanted to Know to Adopt WASM Now!
34mManaging WebAssembly Applications Using Docker and k8s Tooling
37mCRI-O: Under the Hood
31mHow We Can Create a Thriving Wasm Ecosystem
18mCloud Native & WebAssembly: Better Together
25mManaging WebAssembly apps with Kubernetes