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
These bindings seem like they could be interesting in building normal containers which run a Go process and run wasm code. For doing that this runtime would not be necessary.
Is there also bindings or a good way to manage the wasmer runtime? The scope of this Proof of Concept is just to implement to the containerd shim interface which has a basic lower level container process management API. It would be interesting for the lower level wasm runtime to provide all the primitives needed to manage wasm just like any other container, such that the wasm runtime is the secure sandbox with no other overhead.
Hi!
As part of our work in Wasmer, we are working on a Go extension that let anyone use a WebAssembly runtime performantly from Go: https://github.com/wasmerio/go-ext-wasm/
It might be a good use case for containerd-wasm!
Here's an example for it: https://github.com/wasmerio/go-ext-wasm/blob/master/wasmer/test/example_import_test.go
Feel free to close this issue if you think is not relevant to this project... just wanted to show our work as might be useful for this project!
The text was updated successfully, but these errors were encountered: