wasm: add support for wasmedge runtime by ibmibmibm · Pull Request #774

wasm: add support for wasmedge runtime by ibmibmibm · Pull Request #774 · containers/crun

Signed-off-by: Shen-Ta Hsieh <beststeve@secondstate.io>

hydai mentioned this pull request

Nov 19, 2021

flouthoc added a commit to flouthoc/crun that referenced this pull request

Jul 5, 2022

Following PR initiates and adds support for crun to be able to build and
run wasm/wasi workload in a native manner using `wasmtime`.

Crun already supports running `wasm` workload using `wasmer` and `wasmedge`
following PR extends this feature so that end-users can switch to `wasmtime`,
following feature is proposed inorder to maintain feature parity with
other tools in the same space.

Ref:
* Wasmedge integration: containers#774
* Wasmer integration: containers#742

Signed-off-by: Aditya R <arajan@redhat.com>

flouthoc added a commit to flouthoc/crun that referenced this pull request

Jul 5, 2022

Following PR initiates and adds support for crun to be able to build and
run wasm/wasi workload in a native manner using `wasmtime`.

Crun already supports running `wasm` workload using `wasmer` and `wasmedge`
following PR extends this feature so that end-users can switch to `wasmtime`,
following feature is proposed inorder to maintain feature parity with
other tools in the same space like `krustlet` which rely on `wasmtime` under the hood.

Ref:
* Wasmedge integration: containers#774
* Wasmer integration: containers#742
* https://github.com/krustlet/krustlet

Signed-off-by: Aditya R <arajan@redhat.com>

flouthoc added a commit to flouthoc/crun that referenced this pull request

Jul 6, 2022

Following PR initiates and adds support for crun to be able to build and
run wasm/wasi workload in a native manner using `wasmtime`.

Crun already supports running `wasm` workload using `wasmer` and `wasmedge`
following PR extends this feature so that end-users can switch to `wasmtime`,
following feature is proposed inorder to maintain feature parity with
other tools in the same space like `krustlet` which rely on `wasmtime` under the hood.

Ref:
* Wasmedge integration: containers#774
* Wasmer integration: containers#742
* https://github.com/krustlet/krustlet

Signed-off-by: Aditya R <arajan@redhat.com>

flouthoc added a commit to flouthoc/crun that referenced this pull request

Jul 11, 2022

Following PR initiates and adds support for crun to be able to build and
run wasm/wasi workload in a native manner using `wasmtime`.

Crun already supports running `wasm` workload using `wasmer` and `wasmedge`
following PR extends this feature so that end-users can switch to `wasmtime`,
following feature is proposed inorder to maintain feature parity with
other tools in the same space like `krustlet` which rely on `wasmtime` under the hood.

Ref:
* Wasmedge integration: containers#774
* Wasmer integration: containers#742
* https://github.com/krustlet/krustlet

Signed-off-by: Aditya R <arajan@redhat.com>

flouthoc added a commit to flouthoc/crun that referenced this pull request

Jul 11, 2022

Following PR initiates and adds support for crun to be able to build and
run wasm/wasi workload in a native manner using `wasmtime`.

Crun already supports running `wasm` workload using `wasmer` and `wasmedge`
following PR extends this feature so that end-users can switch to `wasmtime`,
following feature is proposed inorder to maintain feature parity with
other tools in the same space like `krustlet` which rely on `wasmtime` under the hood.

Ref:
* Wasmedge integration: containers#774
* Wasmer integration: containers#742
* https://github.com/krustlet/krustlet

Signed-off-by: Aditya R <arajan@redhat.com>

flouthoc added a commit to flouthoc/crun that referenced this pull request

Jul 12, 2022

Following PR initiates and adds support for crun to be able to build and
run wasm/wasi workload in a native manner using `wasmtime`.

Crun already supports running `wasm` workload using `wasmer` and `wasmedge`
following PR extends this feature so that end-users can switch to `wasmtime`,
following feature is proposed inorder to maintain feature parity with
other tools in the same space like `krustlet` which rely on `wasmtime` under the hood.

Ref:
* Wasmedge integration: containers#774
* Wasmer integration: containers#742
* https://github.com/krustlet/krustlet

Signed-off-by: Aditya R <arajan@redhat.com>