wasi-vfs
A virtual filesystem layer for WASI.
NOTICE: This project currently supports only WASI applications on the top of wasi-libc
This project provides a language and host-agnostic virtual filesystem layer for WASI.
Supported filesystems
- Embedded file system: a read only file system embedded in the
.wasm
binary. - to be implemented more...
Installation
A typical installation from the release binaries might look like the following:
$ export WASI_VFS_VERSION=0.1.0
$ curl -LO "https://github.com/kateinoigakukun/wasi-vfs/releases/download/v${WASI_VFS_VERSION}/wasi-vfs-cli-x86_64-unknown-linux-gnu.zip"
$ unzip wasi-vfs-cli-x86_64-unknown-linux-gnu.zip
$ mv wasi-vfs /usr/local/bin/wasi-vfs
Building
To build the project, you need to install the wasi-sdk
version 14.0 or later.
$ export WASI_SDK_PATH=/path/to/wasi-sdk
$ cargo build --target wasm32-unknown-unknown
Demo
Prerequisites
Set $WASI_SDK_PATH
environment variable to the path of the wasi-sdk
(version 14 or later).
Build and run WASI application
$ git clone https://github.com/kateinoigakukun/wasi-vfs.git
$ cd wasi-vfs
# Build libwasi_vfs.a
$ cargo build --target wasm32-unknown-unknown
# Build a WASI app with libwasi_vfs.a
$ $WASI_SDK_PATH/bin/clang -target wasm32-unknown-wasi -o getline.wasm examples/getline.c ./target/wasm32-unknown-unknown/debug/libwasi_vfs.a
# Run the WASI app with --mapdir
$ wasmtime run --mapdir /::./examples/mnt getline.wasm -- /hello.txt
Hello
# Pack ./examples/mnt directory into a WASM binary
$ cargo run -p wasi-vfs-cli -- pack getline.wasm --mapdir /::./examples/mnt -o getline.packed.wasm
# Run the WASM binary again without --mapdir
$ wasmtime run getline.packed.wasm -- /hello.txt
Hello
Testing
Unit tests
$ CARGO_TARGET_WASM32_WASI_RUNNER=wasmtime cargo test --target wasm32-wasi
End-to-end tests
$ cargo build --target wasm32-unknown-unknown
$ LIB_WASI_VFS_A=$PWD/target/wasm32-unknown-unknown/debug/libwasi_vfs.a ./tools/run-make-test.sh
How does it work?
wasi-vfs pack
command is a wrapper of wizer
, which is a pre-initializer for Wasm applications. The initialization process scans the mapped directories, then copies them into in-memory virtual filesystem.
Limitations
Currently, this project only supports WASI applications on the top of wasi-libc because of the following reasons:
This project depends on wasm-ld
and wasi-libc
's imported symbol behavior. wasi-libc
declares some external symbols to import WASI functions in C like below. When __imported_wasi_snapshot_preview1_fd_read
is not defined in any input object files, wasm-ld
produces a (import "wasi_snapshot_preview1" "fd_read")
entry. This is how wasi-libc
calls WASI functions.
int32_t __imported_wasi_snapshot_preview1_fd_read(int32_t arg0, int32_t arg1, int32_t arg2, int32_t arg3) __attribute__((
__import_module__("wasi_snapshot_preview1"),
__import_name__("fd_read")
));
This project exploits that external symbols to hook WASI function calls by defining them in libwasi_vfs.a
. If those symbols are defined, wasm-ld
doesn't produce import entries, and it links symbols normally.
Therefore, this project currently doesn't support Rust application, which calls WASI functions directly without using wasi-libc
.
After module-linking and interface-types will be merged, and WASI will adopt shared-nothing architecture, this project will be able to support all WASI applications.