Pierre

I'd love to see that feature added to the next release's roadmap ^^

Hi. I had a few issues creating my own, especially while trying to understand how the registry crawler works. As I couldn't find any answers to most of my questions...

Links are all 404'ed

This might be a good template: https://hackingcpp.com/cpp/cheat_sheets.html

I'm exploring the GSC path. I had to make a custom version of NodeRed's image (to be based on ubuntu), make use of [non-root PR](https://github.com/gramineproject/gsc/pull/60), I finally got the GSC...

Ok, added the `sys.insecure__allow_eventfd = true` command to the manifest, it works a bit better. Still not completely though, [here is the log](https://gist.github.com/p-vernaeckt/8267e2a98e6b0b39148ebacc1739aad1) (it's a bit too big to fit...

Darn, the gist cut the log by about a half... Ok, here is the interesting part of the log (aka "the end of it"): ``` [P1:T1:node] trace: ---- shim_futex(0x9f4c0910, FUTEX_CLOCK_REALTIME|FUTEX_WAIT_BITSET,...

Same result, no Js error this time though: ``` [P1:T1:node] trace: ---- return from shim_futex(...) = 0x0 [P1:T1:node] trace: ---- shim_futex(0xc3826910, FUTEX_CLOCK_REALTIME|FUTEX_WAIT_BITSET, 4, 0, 0, -1) ... [P1:T1:node] warning: Ignoring...

I activated the most verbose logging mode in node red, launched the docker image as-is, NodeRed indeed logs a lot of info to the console and launches fine. Gamine build/sign...

From [the doc](https://gramine.readthedocs.io/projects/gsc/en/latest/#using-gramine-s-trusted-command-line-arguments), gsc build uses the docker image's entrypoint. The [OpenVino example](https://github.com/gramineproject/gsc/tree/master/Examples/openvino) confirms that too.