docs: fix outdated KinD quickstart example#300
Open
ravindra-RKB wants to merge 1 commit into
Open
Conversation
Signed-off-by: Ravindra Kumar Bundela <ravindrarkb1205@gmail.com>
0b8c954 to
a73ce54
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR updates the KinD quickstart documentation to use a working example configuration.
Background
Issue #1844 reported that the documented example fails with an Exec format error when following the KinD quickstart guide.
Changes
Replace wasmedge/example-wasi:latest
with hydai/wasm-wasi-example:with-wasm-annotation
Replace module.wasm.image/variant=compat-smart
with module.wasm.image/variant=compat
Update both occurrences in docs/develop/deploy/kubernetes/kind.md
Verification
The updated commands match the working configuration described in Issue #1844 and the upstream kind-crun-wasm example.
Type of Change
Documentation update
Related Issue
Fixes WasmEdge/WasmEdge#1844