Federico Di Pierro

/milestone 0.36.0

/remove-lifecycle stale

Hi! > sudo ln -s /root/.falco/4.0.0+driver/x86_64/falco_ubuntu-generic_5.15.0-72-generic_79.ko /lib/modules/$(uname -r)/falco.ko Yep this is something known; i tried to address it but had to revert it for reasons: https://github.com/falcosecurity/falco/pull/2388, that reverted https://github.com/falcosecurity/falco/commit/308736280dc70289511111dd094e193639f72cff. /cc...

I see 2 fixes for this: * https://github.com/falcosecurity/falco/pull/2773 -> to allow users without `dialog` package to still retain the possibility to customize the driver being automatically installed * making [falco-kmod.service](https://github.com/falcosecurity/falco/blob/master/scripts/systemd/falco-kmod-inject.service#L10C17-L10C25)...

For the latter one, we need to make sure that the driver is always copied to `/root/.falco/$driver_version/$arch/foo.ko`. This is already done by the new falcoctl driver-loader implementation that will be...

Indeed, we cannot change falco-kmod.service: for host installation the kmod is always expected to be installed via `dkms` to ensure that it gets properly bumped in case the user upgrades...

FALCO_DRIVER_CHOICE and the new falcoctl based driver-loader are now on Falco master. I think we can close this one. /close

Hi! If you upgraded the running kernel, Falco driver needs to be upgraded as well (ie: rebuilt). For the moment, we are not able to provide prebuilt drivers for linux...

/remove-lifecycle rotten Hi! We do now support building drivers for kernels > 5.10 ;) Is this still an issue? See: https://download.falco.org/driver/site/index.html?lib=4.0.0%2Bdriver&target=ubuntu-generic&arch=all&kind=all

Hi! Thanks for opening this feature request! PRs to support Talos are opened; microOS might as well gets its support too! We recently shared a blog post about integrating support...