Contain Yourself: Wasm and the OCI Spec
summary
Demonstrates the wasm OCI artifact spec by compiling C and Go components, publishing them with wash/wack tooling to an OCI registry, and pulling the same artifact into wasm-time, wasmCloud, and a containerd runWASI shim on Kubernetes via a runtimeClass. The components return a hello response and run unchanged across Windows, Linux VMs and a kind cluster — shown working in three or four different runtimes — proving cross-platform artifact reuse end to end.
AI-written summary · about
chapters (7)
- 0:00Introductions and agenda
- 1:44OCI and Wasm integration
- 5:38Glossary of Wasm terms
- 7:17The Wasm OCI specification
- 11:01Technical demos
- 26:09Future plans
- 28:59Call to action and Q&A
related talks
10mEverything You Wanted to Know to Adopt WASM Now!
18mCloud Native & WebAssembly: Better Together
38mCRI-O's WASM Adventure: Challenges, Strategies, and What Lies Ahead
33mKubernetes on the edge: running low-latency workloads with WebAssembly
31mHow We Can Create a Thriving Wasm Ecosystem
30mWASM in the Wild West: A Practical Application Tale
34mContainers vs. WebAssembly: What's the Difference and Which Should I Use?
07mBeyond The Browser: Wasm in Your Cloud Development Workflow