Distributing and Running Containers for Wasm-Enabled Environments
summary
container2wasm runs unmodified Linux containers inside Wasm VMs by CPU emulation and in-browser mounting, offering both c2w conversion blobs and an image mounter that fetches OCI images directly into the browser without conversion. a QEMU port (qemu-wasm) supplies 64-bit and AArch64 guests, JIT via TCG-to-wasm and multicore support; a gzip/pigz benchmark shows the QEMU path far outperforms the previous box interpreter (box >40s, qemu much faster). features remain experimental: networking and preinit are limited, cold starts are slow, and public registries need CORS.
AI-written summary · about
chapters (17)
- 0:00Running containers on Wasm
- 1:02Porting Linux apps to Wasm
- 2:51Container to Wasm tool
- 4:40Containers to browsers
- 7:09Demo: unmodified container images
- 10:12What is QEMU
- 11:39Porting QEMU to Wasm
- 14:40QEMU Wasm performance
- 18:43Demo: multicore emulators
- 20:52Demo: ARM64 in browser
- 21:56Use cases and future work
- 23:43Demo: emulated Raspberry Pi
- 24:54Future improvements
- 27:09Proposing CNCF project
- 27:56Comparison with projects
- 29:24Summary
- 29:45Q&A
related talks
05mContainer2Wasm: Running Containers On Wasm Environments
36mFetching and Running Container Images on Browsers
28mRunning Linux-Based Containers on Wasm and Browser with Container2wasm Converter
07mBeyond The Browser: Wasm in Your Cloud Development Workflow
32mMoving Beyond Containers - Introducing Boxer
34mContainers vs. WebAssembly: What's the Difference and Which Should I Use?
41mOptimizing Microservices with WebAssembly and Linux Containers: Exploring Hybrid Contain...
32mDocker + WebAssembly