Repository navigation
wasmtime-wasi only preopening the first and last directory set in WasiCtxBuilder #10058
Description
Test Case
Clone example repo here: https://github.com/justingaffney/wasmtime-preopen-bug
Steps to Reproduce
- Build component
cd componentcargo component build --release
- Run host
cd ..cargo run
Expected Results
The following output:
Reading /a: Success
Reading /b: Success
Reading /c: Success
Reading /d: Success
Reading /e: Success
Actual Results
The following output:
Reading /a: Success
Reading /b: Failed. Error: Some(Custom { kind: Uncategorized, error: "failed to find a pre-opened file descriptor through which \"/b\" could be opened" })
Reading /c: Failed. Error: Some(Custom { kind: Uncategorized, error: "failed to find a pre-opened file descriptor through which \"/c\" could be opened" })
Reading /d: Failed. Error: Some(Custom { kind: Uncategorized, error: "failed to find a pre-opened file descriptor through which \"/d\" could be opened" })
Reading /e: Success
Versions and Environment
Wasmtime version or commit: 28.0.1, 29.0.0
Operating system: Windows 11
Architecture: x86_64
Activity
justingaffney commentedon Jan 21, 2025
I just tried it on Ubuntu 24.04.1 and have the same issue
Fix a missing increment in p1-to-p2 adapter
alexcrichton commentedon Jan 21, 2025
Thanks for the report! This should be fixed in #10064. I'll note though that this is a bug in the "adapter" which will take a bit of time to propagate to toolchains. In the meantime working around this will be difficult as the adapter is pretty deep inside tooling and difficult to update-on-a-dime.
Fix a missing increment in p1-to-p2 adapter (#10064)
Fix a missing increment in p1-to-p2 adapter (bytecodealliance#10064)
[29.0.x]: Fix a missing increment in p1-to-p2 adapter (#10067)
Update the adapter binaries cargo-component uses
Update adapter builds
Update adapter builds (#56)
Update wasm-component-ld
Update wasm-component-ld
Update the adapter binaries cargo-component uses (#370)
Update the `wasm-component-ld` tool
Rollup merge of rust-lang#135850 - alexcrichton:update-wasm-component…
justingaffney commentedon Jan 22, 2025
Thanks for the fast response!
It looks like the adapter is used in quite a few places, and I'm not sure how it all fits together yet. In the case of my example repo would I just need the next release of cargo-component, that contains your merged PR updating
wasi-preview1-component-adapter-provider? Then I'd just need to runcargo component buildagain to include the new adapter version in the produced .wasm file?alexcrichton commentedon Jan 22, 2025
I believe that should work yeah!
Rollup merge of rust-lang#135850 - alexcrichton:update-wasm-component…
Update wasm-component-ld (#506)