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.

Sign up for GitHub

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

Jump to bottom

Filesystem interception #238

Open
chutchinson opened this issue Mar 31, 2023 · 1 comment
Open

Filesystem interception #238

chutchinson opened this issue Mar 31, 2023 · 1 comment

Comments

@chutchinson
Copy link

Is it possible with these bindings to intercept filesystem operations, or would one have to redefine WASI functions such as fd_read, fd_write, etc? Is a virtual filesystem implementation or filesystem interception supported by wasmtime (but perhaps not this binding? I may be interested in that contribution).
@peterhuene
Copy link
Member

peterhuene commented Apr 2, 2023 •
edited
Loading

I don't believe any of the Wasmtime language bindings make it easy to implement an alternative WASI implementation for intercepting certain operations.

Wasmtime (and these bindings) allow for alternative, host-defined WASI-named functions to be defined in a Linker (for example), but you would need to supply your own implementation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@peterhuene @chutchinson