Introduction
WasmEdge could be integrated with the existing cloud-native infra seamlessly. So developers can leverage container tools such as Kubernetes, Docker, and CRI-O to deploy, manage, and run lightweight WebAssembly applications. This chapter will demonstrate how Kubernetes ecosystem tools work with WasmEdge WebAssembly applications.
Several options exist to manage WASM apps as “containers” under Kubernetes. Both options will give you a Kubernetes cluster that runs Linux containers and WASM containers side by side.
With containerd-shim
Option #1: is to use a containerd-shim to start WASM "containers" via runwasi. Basically containerd could look at the image’s target platform. It uses runwasi if the image is wasm32 and runc if it is x86 / arm. Currently, Docker and Microsoft prefer this approach, which is also the basis for the Docker + WASM preview. Based on containerd
The following image shows how it works.
With crun
Option #2 is to use an OCI runtime called crun (the C version of runc, mainly supported by Red Hat). crun decides whether an OCI image is wasm or Linux based on image annotations. If the image is annotated as wasm32, crun will bypass Linux container setup and just use WasmEdge to run it. Based on crun, we can get the entire Kubernetes stack CRI-O, containerd, Podman, kind, micro k8s, k8s etc to work with WASM images.
With youki
Option #3 is to use an OCI runtime called youki (the Rust version of runc). Like crun, youki decides whether an OCI image is wasm or Linux based on image annotations. If the image is annotated as wasm32, youki will bypass Linux container setup and just use WasmEdge to run it. Based on youki, we can get the entire Kubernetes stack CRI-O, containerd, Podman, kind, micro k8s, k8s etc to work with WASM images.
Both crun and youki could use the following image to show how it works.
Examples we covered
This section will show how to manage WASM App in three different ways. The goal is to load and run WebAssembly OCI images alongside Linux OCI images (e.g., today's Docker containers) across the Kubernetes stack.
We will cover two different demos in most cases. We built them from Rust source code, built OCI images around them, and then published them to Docker Hub. You can find the more container example here.
Since we have already built and published those demo apps on Docker Hub, you could also pull the images from Docker Hub. If you want to build your own WASM image, please refer to this article.
Since we have already built and published those demo apps on Docker Hub, you could also just go straight to the container runtime sections to use these images.
Let's get started.