You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, I try to add support for wasm-micro-runtime (WAMR) as another handler. It seems promising since it is a very lightweight WASM runtime.
I have followed the implementation of current handlers as well as docs regarding embedding WAMR, but unfortunately, I failed to succeed. Here is the PR with my efforts.
Would someone be able to help me fix it? Currently, it seems that the wasm module is not executed, regarding the "Running" status reported by kubectl.
I'm using Kubernetes 1.27, containerd 1.6, latest build of crun and WAMR.
The text was updated successfully, but these errors were encountered:
Hi, I have updated my PR and it does work! It is not yet fully developed and needs some polishing but the WASM containers are executing.
The env vars are being passed and you can see the container logs. The memory footprint is much much lower than the one of Wasmedge. Simple wait containers use about 54% less memory due to the WAMR library being super lightweight!
Hello, I try to add support for wasm-micro-runtime (WAMR) as another handler. It seems promising since it is a very lightweight WASM runtime.
I have followed the implementation of current handlers as well as docs regarding embedding WAMR, but unfortunately, I failed to succeed. Here is the PR with my efforts.
Would someone be able to help me fix it? Currently, it seems that the wasm module is not executed, regarding the "Running" status reported by kubectl.
I'm using Kubernetes 1.27, containerd 1.6, latest build of crun and WAMR.
The text was updated successfully, but these errors were encountered: