Skip to content
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

Reversed WASI interfaces? #57

Open
ZheniaZuser opened this issue May 18, 2024 · 1 comment
Open

Reversed WASI interfaces? #57

ZheniaZuser opened this issue May 18, 2024 · 1 comment

Comments

@ZheniaZuser
Copy link

ZheniaZuser commented May 18, 2024

I have the use case about which I am not sure if currently possible/handled:
Virtual File system consumed by host. For example:
virtual disk file on host's FS > wasm component that reads it through wasi-fs and gives read\write access to it's encapsulated FS through wasi-fs interface that is exposed to host > and is consumed by "wasi-fs to WinFSP adapter" giving access to the FS to all Windows software (and similarly "wasi-fs to FUSE adapter" on Linux).

@guybedford
Copy link
Collaborator

Component binaries need to at the root reference host-supported WIT. So if you wanted to output a component that binds to WinFSP, the first step would be to create a host implementation of these bindings for the component model, defined in a WIT package.

Given such a host interface and implementation, creating an FS adapter to this implementation can be achieved very similarly to how WASI-Virt works, but it would likely be more like a fork of WASI-Virt to achieve the use case given the specific nature of the target bindings.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants