No explict ways to tell the wasm runtime what file and directory wasm binary has access to

[Mossaka]

          This is from a discussion at the CG meeting this week. Runwasi currently has no ways to specify, explicitly, what file and directories a wasm container have access to.

Originally posted by @Mossaka in #142 (comment)

[jsturtevant]

This came up a bit in the OCI artifact conversation as well. See the Open Questions and Phase 3 in sections in Wasm OCI Artifacts in Containerd. I am really curious in the usecases for file access, and if they can be solved via volumes or not. This could also be input into possible runtime spec/image spec changes need to support wasm functionality fully.