Runners and wasmer_wasix::wapm
don't take the [fs]
table into account
#3744
Labels
Milestone
wasmer_wasix::wapm
don't take the [fs]
table into account
#3744
Describe the bug
The current runner implementation (used by
wasmer run
andwasmer run-unstable
) don't respect the directory mappings in thewasmer.toml
file's[fs]
table.Steps to reproduce
The easiest way to reproduce this is by creating a package that will serve static files, where the original location on the publishing machine's filesystem doesn't match the directory the WASI executable will see.
Expected Solution
There are two ways we could resolve this.
The first one is by making sure consumers of a
*.webc
file respect the[fs]
mapping. At the moment our runners use the naiveWebcFileSystem::init_all()
method to set up the volumes (here), and that just implements a poor man's unionfs with all the volumes.Alternatively, the
wapm-targz-to-pirita
could shuffle directories around as part of the general tarball-to-webc conversion.The text was updated successfully, but these errors were encountered: