bytecodealliance / wasm-tools

CLI and Rust libraries for low-level manipulation of WebAssembly modules
Apache License 2.0
1.35k stars 245 forks source link

wasi-virt throws error in wasm-compose (redirected from wasi-virt to Wasm-tools) #1565

Open thesuhas opened 6 months ago

thesuhas commented 6 months ago

Hi,

I'm trying to use wasi-virt with a micro service that I have written in rust. I want to give it a pre-opened file directory so that I can read a json file. I am using this command: wasi-virt --debug --stderr=allow composed-cinema.wasm --preopen microservices/cinema-1/users=/data --allow-http -o virt-cinema.wasm And I get the following error: image

It seems to be an error in wasm-compose. For some additional context, the micro service was composed by using the http@3.0 draft from here.

I initially posted this in wasi-virt but was redirected here as it was an issue stemming from wasm-tools.

rvolosatovs commented 2 months ago

Looks like I just hit the same issue #1811

alexcrichton commented 1 month ago

Would it be possible to get a standalone invocation of wasm-tools compose to reproduce this @rvolosatovs perhaps? (or @thesuhas, but I realize it's been awhile since you originally opened this). If that's possible it might be best to try out such an invocation with wac as well. If it works in wac and doesn't work with wasm-compose then the best solution here is to probably migrate wasi-virt to wac instead of wasm-compose.

brian14708 commented 1 month ago

I’ve been encountering a similar problem. When custom component functions references wasi: resources, it will fail to compose with wasi-virt.

Here is a minimal reproducible example: https://github.com/brian14708/wasm-tools-1565