New issue
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
run component in docker #8411
Comments
Sorry but can you expand the problem you're having a bit more? I think that most of us working on Wasmtime aren't familiar with |
Sorry for being so bad.
is to prove the gitexample is working. When I use docker it is similar to use configure containerd/runwasi. But I got no way to tell the shim (or runwasi) to use the server subcommand. like in runwasi/containnerd wasmtime is executing the entrypoint of an container/image. Rephrased: How does wasmtime in docker/runwasi etc. knows it has to run the/a component. |
Hi @hone, thx for checking.
Using the wasmtime (containerd-shim) I need a (wasm) container.
This kind of images expect the wasm module as ENTRYPOINT. So is there a way to tell the shim to use a special subcommand. |
@erkules did you resolve this? I am looking to do exactly this right now as well. But I think like @alexcrichton this is not a wasmtime issue, it's a docker issue. |
@matsbror haven't solved it.
containerd-logs:
|
I did some research on this and the problem lies in |
Hey runwasi maintainer here. Yes I agree that this is an runwasi issue, probably not related to wasmtime. As @matsbror mentioned, there is no support for
You assessment is right. The wasmtime shim in Docker is using the wasmtime SDK directly, and thus there is no subcommand for serving HTTP requests.
The shim will parse the first few bytes of the binary and determine whether it's a wasm module, a wasm component, or something else. If it's a wasm component, it assumes the component implmenets the In the meantime, if you just want to run |
I bulid https://github.com/sunfishcode/hello-wasi-http
wasmtime serve works
I got docker configured to have wasmtime as runtime. works with non-proxy wasm:
But I didn't found how to configure the image to tell the runtime to use the subcommand.
The text was updated successfully, but these errors were encountered: