We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I have compiled and installed the wasmtime shim (and wasmedge and wasmer), and I am able to run a wasm module using docker:
docker run --rm --runtime io.containerd.runtime.wasmtime.v1 matsbror/serwasm2:0.1
However, I would like to run it directly using ctr if possible, but I get this error:
ctr
sudo ctr run --rm --runtime io.containerd.runtime.wasmtime.v1 docker.io/matsbror/serwasm2:0.1 myapp bogus ctr: failed to create shim task: Others("exec process failed with error error in executing process : wasmtime executor can't handle spec"): unknown
I can run a spin app directly using ctr with the spin shim from spinkube.
The text was updated successfully, but these errors were encountered:
It's hard to tell what's going on with this error, and perhaps it would be helpful to add containerd logs.
containerd
If you are running containerd as a service in Linux, you can check containerd logs by journalctl -u containerd. It seems like this error msg is from https://github.com/containerd/runwasi/blob/main/crates/containerd-shim-wasm/src/sys/unix/container/executor.rs#L40
journalctl -u containerd
Sorry, something went wrong.
Same error here but inside a pod of Kubernetes (Kind) and using WasmEdge. Kubectl logs empty.
Any ideas?
Executor::exec
The error message should be more explicity after #655.
No branches or pull requests
I have compiled and installed the wasmtime shim (and wasmedge and wasmer), and I am able to run a wasm module using docker:
However, I would like to run it directly using
ctr
if possible, but I get this error:I can run a spin app directly using
ctr
with the spin shim from spinkube.The text was updated successfully, but these errors were encountered: