flouthoc commented on issue #358:
Hi Team,
If I read the issue correctly I am working on similar feature for
crun(OCI-runtime) which already supportswasmedgeandwasmerand following PR adds supports forwasmtimehandler in crun: https://github.com/containers/crun/pull/963 feel free to give it a try :)Thanks
flouthoc edited a comment on issue #358:
Hi Team,
If I read the issue correctly I am working on similar feature for
crun(OCI-runtime) which already supportswasmedgeandwasmerand following PR adds supports forwasmtimehandler in crun: https://github.com/containers/crun/pull/963 feel free to give it a try :)Edit: Small doc which shows how to use this feature on kubernetes setup https://github.com/containers/crun/blob/main/docs/wasm-wasi-on-kubernetes.md
Thanks
jwcesign commented on issue #358:
Any updates?
thomastaylor312 commented on issue #358:
@jwcesign There is a group of us from the CNCF Wasm WG that is nearing completion of a spec definition for this. You can find meeting notes here and the working doc here
fitzgen closed issue #358:
Hi all, recently I found an experiment project called containerd-wasm developed by containerd team, and I believe it's a fantanstic idea to combine container management layer (such like Docker and Kubernetes) with wasm runtime.
But for now this project is at very early stage, to make the idea of integrating wasmtime with containerd seamlessly, I pulled an issue https://github.com/dmcgowan/containerd-wasm/issues/2 to improve the portability and performance of this solution.
With this improvement, we can leverage the container ecosystem (
ease of use,widely adopted) and wasm runtime through OCI runtime specification.Any thoughts?
fitzgen commented on issue #358:
Closing this issue as out-of-scope for Wasmtime itself. There are a variety of nascent projects to do this kind of thing and more can always be built on top of Wasmtime. Thanks.
Last updated: Jun 01 2026 at 09:49 UTC