runw icon indicating copy to clipboard operation
runw copied to clipboard

Results 15 runw issues
Sort by recently updated
recently updated
newest added

It seems that runw has a memory leak issue. ![image](https://user-images.githubusercontent.com/45785633/126456180-17ee78cc-d431-4454-a8f5-1b16243fd3c3.png) ![image](https://user-images.githubusercontent.com/45785633/126456205-e1e639ac-ffb1-4b3a-93c4-7405c15875bc.png)

We need to allow the user to restrict resources (CPU, RAM) to the runw payload.

feature request

We would like to support cgroupfs as a fallback cgroup driver when the system does not have systemd.

enhancement

The --allow-command option is not working properly. The command name in the system call is wrong (eg it uses http_proxyhttp_proxy instead of the correct http_proxy)

bug

We need to support WasmEdge interpreter mode in runw so that it can run the ARM32 build.

enhancement

hello dir only contains running wasm: wasi_example_main.wasm (provided by runw project wiki) operate step: 1 ./runw --systemd-cgroup create --bundle=hello --pid-file=pid.txt test first result is running successfully, print necessary messages like...

bug
help wanted

simple go code: `package main import "fmt" func main() { fmt.Println("Hello, WebAssembly!") }` go build cmd: GOARCH=wasm GOOS=js go build -o test.wasm test.go runw run bundle include test.wasm: find /tmp/runw.log...

question

Run `clang-format-12 -i -style=file **/*.h **/*.cpp **/*.in`