Stream: wasmtime on k8s

Topic: No shared spec for OCI + wasm

view this post on Zulip flouthoc (Aug 26 2022 at 05:11):

Hi Folks,

I must be overthinking this and I am not even sure if this is a legit problem. But while working on trying to integrate WASM with OCI runtime, I face this issue sometimes i.e in order to toggle features related to wasm runtime from container images, we only have one method which is annotations and no common standard like we have OCI spec as a result I think each OCI+wasm implementation might end up with their own standards/annotations instead of following a common spec.

For example this will happen here https://github.com/containers/crun/pull/985#issuecomment-1211910701 and I'm sure i will hit this problem again implementing other features as well.

Github might be the best place to discuss this, but I want to know if other folks see this is as a problem as well or is it just me overthinking.

wasmtime: always grant `filesystem capability` for workdir inside container by flouthoc · Pull Request #985 · containers/crun
Following PR introduces two changes. * wasmtime: inherit argv from handler argument instead of process libwasmtime_exec already passes argv which is generated from args provided to container so use...

Last updated: Dec 13 2025 at 17:03 UTC