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

[thesuhas]

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:

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]

Looks like I just hit the same issue #1811

[alexcrichton]

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]

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