stevenj opened issue #8963:
Our implementation requires filesystems to be fully controlled, and files come from a VFS not any mounted filesystem.
That means we need to control the low level aspects of filesystem access for WasiP2.I don't see how that can be achieved, because the only option I see is giving Wasi access to a pre-opened directory, which is 100% off the table for our application. How to use the WaiCtxBuilder, and abstract the necessary filesystem interfaces to the runtime?
alexcrichton commented on issue #8963:
For a fully virtual filesystem you won't be using
WasiCtxBuilder
. You'll want to instead implement theHost
traits directly generated in thewasmtime-wasi
crate such as this. You'd then calladd_to_linker
or similarly.
Last updated: Dec 23 2024 at 12:05 UTC