Comment by westurner

How to compile the userspace, though?

Have you seen container2wasm or ktock/vscode-container-wasm?

container2wasm: https://github.com/container2wasm/container2wasm

ktock/vscode-container-wasm: https://github.com/ktock/vscode-container-wasm

ktock/vscode-container-wasm-gcc-example: https://github.com/ktock/vscode-container-wasm-gcc-example

From joelseverin/linux-wasm: https://github.com/joelseverin/linux-wasm :

> Hint: Wasm lacks an MMU, meaning that Linux needs to be built in a NOMMU configuration. Wasm programs thus need to be built using -fPIC/-shared. Alternatively, existing Wasm programs can run together with a proxy that does syscalls towards the kernel. In such a case, each thread that wishes to independently execute syscalls should map to a thread in the proxy. The drawback of such an approach is that memory cannot be mapped and shared between processes. However, from a memory protection standpoint, this property could also be beneficial.