Running Linux-Based Containers on Wasm and Browser with Container2wasm Converter
summary
Converter based on BuildKit turns a Linux container into a single Wasm image that runs the guest kernel and userland via CPU emulators compiled to Wasm, enabling container2wasm output that supports WASI and two networking modes: host-side c2w_net proxy or browser-only fetch proxy. Demos run Debian x86_64 in-browser and a VS Code web extension mounts /workspace, but images are large (~200 MB for Debian x86_64) and no benchmarks exist yet so CPU emulation overhead (no JIT) is expected.
AI-written summary · about
chapters (10)
- 0:00Container to Wasm converter intro
- 1:50Porting apps to Wasm challenges
- 3:17How converter works
- 5:49Running containers in browser
- 7:56Live Debian demo in browser
- 9:46Conversion process details
- 13:20VS Code extension
- 16:20Use cases beyond browsers
- 17:27Future improvements & limits
- 19:33Q&A
related talks
36mFetching and Running Container Images on Browsers
31mDistributing and Running Containers for Wasm-Enabled Environments
05mContainer2Wasm: Running Containers On Wasm Environments
41mOptimizing Microservices with WebAssembly and Linux Containers: Exploring Hybrid Contain...
32mDocker + WebAssembly
07mBeyond The Browser: Wasm in Your Cloud Development Workflow
31mWebAssembly & Containers: The Power Couple
37mDevelop Wasm Applications with Docker