-
Notifications
You must be signed in to change notification settings - Fork 311
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Supporting additional WASM runtime #1303
Comments
we can add other runtimes, you can take a look at the existing ones for an idea of how it should be done. The support for a specific handler must be specified at configure time Are you interested in working on it? |
@hardiksd Have you looked at |
Thanks. Yes, I can work and enable WAMR runtime. It has much smaller footprint compared to wasmtime. I went through old commit's to see how this can be done. So I should be able to work on it. Thanks for the pointers. |
@hardiksd do you have any progress with the work on adding wamr support? |
Hello, I have created a PR with a preview of WAMR runtime implementation. 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! It seems very promising! |
Hi, I'm new here but exploring using crun on baremetal linux embedded system. Going through the build files I figure WASM is supported experimentally and few WASM runtime options are available.
I wanted to know what would be good place to look into adding one more wasm runtime. I'm specifically interested in adding WAMR and hoping it can be added as one additional option for WASM - https://github.com/bytecodealliance/wasm-micro-runtime
any pointers would be helpful.
The text was updated successfully, but these errors were encountered: