Federico Di Pierro
Federico Di Pierro
/cc @LucaGuerra PTAL :)
@Andreagit97 i enabled back driver loader tests on arm64 too, now! Since we now have actuated arm64 node that runs ubuntu, we should be able to run them!
> Error: JavaScript Actions in Alpine containers are only supported on x64 Linux runners. Detected Linux Arm64 Oh wow. Feature request: https://github.com/actions/runner/issues/801 It seems like we are out of luck...
I will close this one since it cannot be supported right now; and open a new PR with only the `driver-loader` enablement for arm64 part.
Hey! Thank you for this very detailed issue! We will look into it asap! > Today I tried to run Falco without systemd service on Vault nodes and so far...
From `pstree` man pages: > Child threads of a process are found under the parent process and are shown with the process name in curly braces, e.g. > > icecast2---13*[{icecast2}]...
Also there is no real difference between Falco 0.32 unit (that was kmod only though) and Falco 0.35 falco-bpf unit: * [0.32.0](https://github.com/falcosecurity/falco/blob/f9b0568187424d11bf871d3de8c2cd44c139c21f/scripts/debian/falco.service) * [master](https://github.com/falcosecurity/falco/blob/master/scripts/systemd/falco-bpf.service)
Hi! Thanks for this PR! > echo " --source-only skip execution and allow sourcing in another script" This is from the help message of falco-driver-loader. I assume we don't want...
I think it is pretty useful to add the `--print-env` :) I'd also print `TARGET_ID` like https://github.com/falcosecurity/falco/blob/master/scripts/falco-driver-loader#L314 does!