Interesting, to use docker as way to package and run wasm stuff. Actually makes sense from the point of view that it's yet another thing that needs networking, security, etc. Why reinvent all that when we already have docker, docker-compose, kubernetes, etc. as an API to drive all of that. It doesn't matter if underneath it uses wasmer instead of whatever kernel containerization is used for docker, or both. It's just another process that launches.<p>And it kind of solves cross platform distribution since unlike docker images, these should run pretty much on any cpu architecture (as long as it has a wasm runtime).