kateinoigakukun/wasi-vfs

A virtual filesystem layer for WASI.

wasi-vfs's Issues

Preopens & limitations

Great package! Two short questions:

1. I understand the limitations in the readme should be covered now. Is there any other known limitations?
2. Is this approach compatible with preopens from wasi (e.g. pack with vfs, then share an additional directory at wasi init)?

Possibility of adding write capabilities

In theory, is it possible to add write support to the virtual file system? Why/Why not?

Thanks

support arm

 => ERROR [11/11] RUN wasi-vfs pack ruby.wasm --mapdir /src::./src --mapdir /usr::./head-wasm32-unknown-wasi-full/usr -o my-ruby-app.wasm                            0.2s
------
 > [11/11] RUN wasi-vfs pack ruby.wasm --mapdir /src::./src --mapdir /usr::./head-wasm32-unknown-wasi-full/usr -o my-ruby-app.wasm:
#14 0.155 qemu-x86_64: Could not open '/lib64/ld-linux-x86-64.so.2': No such file or directory

fixed it by using docker build --platform linux/x86_64 but would be nice if it just worked

How to use `wasi-vfs` with Python?

I'd like to use wasi-vfs with Python-Wasi, as I've done with Ruby, but it seems something has to be done with the .wasm file before wasi-vfs can add the files. How can I get started? Thank you.

CC: @nickvidal @bstrie

Plans to publish to crates.io?

I would like to experiment with this in a rust project I am working on, and I was hoping to manage it as dependency via cargo/crates.io.

Add `--exclude` option

make mac installs easy

I stopped after the sdk clone was taking >1GB to download

any of these would be nice:

• darwin binaries
• homebrew formula
• copy-pastable clone+build instructions

Duplicate symbols when building with wasi-sdk 20

I was getting a crash when initializing a wasm module that used wasi-vfs. I was using wasi-sdk 20 and thought that maybe I should build wasi-vfs against that to make sure that wasn't the issue. However, after getting it built, I get the following errors when attempting to link libwasi_vfs.a into a module. The libc included with wasi-sdk includes the rintf and rint functions already. I was wondering if you had run across this before, or if this is possibly an addition to one of wasi-vfs' dependencies?

wasm-ld: error: duplicate symbol: rintf
>>> defined in /opt/lib/libwasi_vfs.a(compiler_builtins-d324d30d7b4a99a9.compiler_builtins.50f24778-cgu.60.rcgu.o)
>>> defined in /opt/wasi-sdk-20.0+threads/bin/../share/wasi-sysroot/lib/wasm32-wasi/libc.a(math-builtins.o)

wasm-ld: error: duplicate symbol: rint
>>> defined in /opt/lib/libwasi_vfs.a(compiler_builtins-d324d30d7b4a99a9.compiler_builtins.50f24778-cgu.70.rcgu.o)
>>> defined in /opt/wasi-sdk-20.0+threads/bin/../share/wasi-sysroot/lib/wasm32-wasi/libc.a(math-builtins.o)

Multiple calls to `pack`?

Is it possible to allow multiple calls to wasi-vfs pack? We'd like to add some files to a wasm module as a "standard library", but then add other directories later on with subsequent calls. It appears as though if you do that now, you only get the result of the final call.