Peter Morjan

You just have to follow the [build instructions]( https://github.com/gotoz/runq#developing-runq). And if you don't then the Makefile already fails with an useful error message: ``` Error: RunC source not found To...

Currently runq works on x86_64 and s390x. For AArch64 you would have to copy the architecture specific code in `./qemu` and in `./cmd/proxy/qemu_.go`. Technically it’s also possible to take Qemu...

thanks @yoheiueda on my system the readonly.sh test fails: ``` $ ./test/integration/readonly.sh rc_want=0 rc_given=0 test succeeded: readonly.sh : rootfs is not writable rc_want=0 rc_given=0 test succeeded: readonly.sh : rootfs is...

kind of a hack - but if you put the patch below on top of mqttws31.js and run 'npm install ws' at least the simple examples do work in Node.JS....

@ChristianUlbrich MQTT.js is perfectly ok. Maybe 64 external dependencies isn't that much for the features it supports but a problem of Javascript/Nodejs projects in general. For example https://www.npmjs.com/package/isarray : (used...

Thanks for the update. I understand there is no easy way to solve this. Since I no longer need a fix for this issue feel free to close it. Thanks!

Thanks for the PR. The first commit looks good to me. I think we don't have to support overriding DOCKER_INIT if we instead search for docker-init in $PATH. Your changes...

I'm sorry for the confusing regarding the PATH. In all my systems the mount path is always `/sbin/docker-init`. So your commit is ok. But we could consider removing the check...

If `/sbin/docker-init` does not exist we could simple try to copy from `/usr/libexec/docker/docker-init` to support "modern installs". You can add this to your PR if you like.

Regarding 22.04 I would prefer a second Dockerfile. If we integrate a second distro/version then we must always test and support it. The base kernel modules are copied into the...