Skip to content

develop/deploy: change crun/youki wording in intro#291

Merged
hydai merged 1 commit intoWasmEdge:mainfrom
t4chib4ne:wasm-k8s-intro-wording
Feb 17, 2026
Merged

develop/deploy: change crun/youki wording in intro#291
hydai merged 1 commit intoWasmEdge:mainfrom
t4chib4ne:wasm-k8s-intro-wording

Conversation

@t4chib4ne
Copy link
Contributor

The previous wording stated crun/youki would bypass Linux Containers if WASM was used. This is not true, to the best of my knowledge.

Explanation

crun nor youki skip container creation when running WASM. They use an embedded WASM runtime but still create a container for it. To me the wording sounds like no container would be created so I changed it to explicitly mention the creation of a container.
I also removed the bold formatting at the beginning of the containerd paragraph so they match.

Related issue

What type of PR is this

/kind documentation

Proposed Changes

Clarifies that a container is still created when WASM is executed with crun or youki and explains that both runtimes execute WASM with an embedded WasmEdge.
I think this clarification is important because someone wanting to run a Linux Container and a WASM module side by side in the same Pod might be confused how this is achieved if WASM would not run inside a container.

The previous wording stated crun/youki would bypass Linux
Containers if WASM was used. This is not true.

Signed-off-by: Maximilian Hüter <t4chib4ne@mailbox.org>
@t4chib4ne t4chib4ne force-pushed the wasm-k8s-intro-wording branch from 3b0ac08 to bf73efd Compare February 16, 2026 19:18
@hydai hydai merged commit 97206d5 into WasmEdge:main Feb 17, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants