Docker and WebAssembly: Better Together
summary
Shows that compiling the PHP interpreter with the WASI SDK into a WebAssembly module and running it with the WasmEdge runtime inside Docker Desktop produces tiny OCI images (often tens of megabytes vs hundreds of MB for Linux containers), enforces capability-based isolation (no environment variables or root filesystem access unless explicitly passed), preserves performance close to native, and runs the same module across x86/ARM/RISC-V. Demonstrations include a working PHP CLI, Docker container, Apache module path and WordPress in-browser execution.
AI-written summary · about
chapters (12)
- 0:00Introduction to Wasm
- 0:42What is WebAssembly
- 2:15Wasm in the browser
- 3:31Wasm on the server
- 6:18Evolution of cloud tech
- 8:43Docker and Wasm
- 10:21WasmEdge runtime
- 12:19Porting PHP to Wasm
- 15:03Hands-on Wasm demo
- 17:15Security comparison
- 20:24Docker containers
- 24:02Wasm portability
related talks
41mOptimizing Microservices with WebAssembly and Linux Containers: Exploring Hybrid Contain...
31mWebAssembly & Containers: The Power Couple
34mManaging WebAssembly Applications Using Docker and k8s Tooling
06mLightning Talk: WASM Vs Docker: Partners, Not Rivals
32mDocker + WebAssembly
30mRunning interpreted languages in WebAssembly
42mWebAssembly beyond the browser
48mWebAssembly Beyond the Browser
