runwasi

The way this works is it uses a containerd shim. In containerd-land, shims are responsible for all the platform dependent setup/management of a container. The "normal" shim on Linux is the runc shim (io.containerd.runc.v2). On Windows the shim is called runhcs (io.containerd.runhcs.v1). The docker solution mentioned in the article modifies the "wasmtime" shim from https://github.com/containerd/runwasi so that it uses "wasmedge" instead. It also happens to be using an unreleased version of dockerd. So how does this work with compose? Currently you need to specify the runtime for the container, there should be an option in the compose yaml for this. How does it work with pods? You need to configure containerd's cri config with a runtime handler that specifies the wasmedge shim. Then you add a RuntimeClass to k8s and add that to your pod spe

Yup, but they have a lot of different awesome projects on the fire, it can be hard to know which one to use: - https://github.com/deislabs/runwasi - https://github.com/deislabs/hippo - https://github.com/deislabs/wagi - https://github.com/deislabs/krustlet The description at the end of the article sounds like CGI, on WASM, which is what WAGI is.

Volumes are mapped in already. They get mounted to the containers rootfs dir, and that is used as a preopen for wasi. https://github.com/deislabs/runwasi/blob/9a43a31c1f29df65392...