Moving Beyond Containers - Introducing Boxer
summary
Boxer converts Dockerfiles into runnable Wasm boxes using Marquott to provide a virtualized libc and a Rust VFS, compiling C with clang and linking against the Marquott libs. The prototype implements about 60% of POSIX calls and aims to support ~95% of typical container workloads; a demo builds a box, runs the same C binary locally and in the browser, and swaps runtimes (wen time w zero whammer).
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:02Why developers love containers
- 3:31Building WebAssembly plugin framework
- 5:21Containers vs WebAssembly limits
- 7:50Unix in WebAssembly
- 10:39Marquott: virtualizing libc
- 12:47Boxer architecture
- 14:16Live Boxer demo
- 17:11Universal Boxer deployment
- 18:56Boxer status and goals
- 20:41Boxer impact
- 22:50Q&A
related talks
31mDistributing and Running Containers for Wasm-Enabled Environments
05mContainer2Wasm: Running Containers On Wasm Environments
28mRunning Linux-Based Containers on Wasm and Browser with Container2wasm Converter
36mFetching and Running Container Images on Browsers
07mBeyond The Browser: Wasm in Your Cloud Development Workflow
37mDevelop Wasm Applications with Docker
32mDocker + WebAssembly
31mBuild, Share, Run WebAssembly Apps Using the Docker Toolchain
