Fetching and Running Container Images on Browsers
summary
container2wasm converts Linux containers into Wasm images by packaging CPU emulators (box for x86_64, TinyEMU for RISC‑V), WASI VFS and v9p mounting so unmodified binaries boot in the browser; an alternative fetches OCI image layout over HTTP and extracts on demand using ESRGZ lazy loading and HTTP range requests to avoid full download; networking works either via a host-side c2w_net websocket proxy or purely in‑browser via the fetch API; a VS Code for the Web extension demonstrates compiling and running code entirely inside the browser.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 1:06Porting apps to browsers
- 3:16Container to WASM
- 8:22Debian container demo
- 10:33How Container to WASM works
- 13:51Distributing images to browsers
- 17:56Lazy loading for startup
- 22:45ESRGZ lazy loading benchmark
- 25:59Use cases for containers
- 27:31VS Code extension demo
- 31:56VS Code extension integration
- 32:41Limitations and future
- 34:57WASM app approaches
- 35:42Summary
related talks
28mRunning Linux-Based Containers on Wasm and Browser with Container2wasm Converter
31mDistributing and Running Containers for Wasm-Enabled Environments
05mContainer2Wasm: Running Containers On Wasm Environments
07mBeyond The Browser: Wasm in Your Cloud Development Workflow
31mWebAssembly & Containers: The Power Couple
42mWebAssembly beyond the browser
41mOptimizing Microservices with WebAssembly and Linux Containers: Exploring Hybrid Contain...
32mDocker + WebAssembly