Closed hasakura12 closed 1 year ago
Hi @hasakura12, the chart is deploying Falco 0.31.1
, is that intentional? If yes unfortunately the pre-built modules are not available for your kernel. You should install the kernel headers on the machines where you are installing Falco and the Falco pod will try to build the kernel module for you.
Anyway you can check here if the prebuilt module exists for your kernel: https://download.falco.org/driver/site/index.html?lib=3.0.1%2Bdriver&target=amazonlinux2&arch=x86_64&kind=kmod
@alacuku
the chart is deploying Falco 0.31.1, is that intentional?
Not intentional. I just want to deploy Falco tbh, and I did it a few months ago and it was working until a few weeks back.
Do you suggest other working version instead?
Do you suggest other working version instead?
Unfortunately, the pre-built module for amazonlinux2_5.4.214-120.368 is not available yet. You should install the kernel header in order to get falco to work. Otherwise, you can wait until the kernel-crawler finds the new kernel and our test-infra builds it.
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close
.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten
.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close
.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle rotten
Is there any update on this? Running also in this issue...
Hi @dcardellino, kernel modules
not being available for a given kernel version is not a chart's issue. You have three options:
falco-driver-loader
will build the module before running falco.@alacuku So I installed the kernel headers like you said but now I got some other weird error message 🤷♂️
falco-driver-loader warning: the compiler differs from the one used to build the kernel
falco-driver-loader The kernel was built by: gcc (Ubuntu 11.3.0-1ubuntu1~22.04) 11.3.0
falco-driver-loader You are using: gcc-8 (Debian 8.3.0-6) 8.3.0
falco-driver-loader CC [M] /var/lib/dkms/falco/4.0.0+driver/build/main.o
falco-driver-loader gcc-8: error: unrecognized command line option '-mharden-sls=all'; did you mean '-mhard-float'?
falco-driver-loader make[2]: *** [scripts/Makefile.build:297: /var/lib/dkms/falco/4.0.0+driver/build/main.o] Error 1
falco-driver-loader make[1]: *** [Makefile:1906: /var/lib/dkms/falco/4.0.0+driver/build] Error 2
falco-driver-loader make[1]: Leaving directory '/host/usr/src/linux-headers-5.15.0-69-generic'
falco-driver-loader make: *** [Makefile:16: all] Error 2
It seems that the falco-driver-loader
does not have an up to date compiler for your kernel. Maybe @FedeDP could help us here.
Yep, unfortunately the falco-driver-loader image ships "old" gcc versions (up to gcc 8), and it is not capable of building recentish kernels like 5.0+.
falco-driver-loader The kernel was built by: gcc (Ubuntu 11.3.0-1ubuntu1~22.04) 11.3.0 falco-driver-loader You are using: gcc-8 (Debian 8.3.0-6) 8.3.0
Btw kernel-crawler did find your kernel: https://falcosecurity.github.io/kernel-crawler/?arch=x86_64&target=Ubuntu&search=5.15.0-69-generic. It is also available on download.falco.org: https://download.falco.org/driver/site/index.html?lib=4.0.0%2Bdriver&target=ubuntu-generic&arch=x86_64&kind=kmod&search=falco_ubuntu-generic_5.15.0-69-generic_76.ko
You should be able to download it!
PS: the drivers for this kernel were built yesterday: https://prow.falco.org/view/s3/falco-prow-logs/logs/build-new-drivers-ubuntu-generic-5-postsubmit/1642897668080406528 :)
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen
.
Mark the issue as fresh with /remove-lifecycle rotten
.
Provide feedback via https://github.com/falcosecurity/community. /close
@poiana: Closing this issue.
Describe the bug
How to reproduce it
Expected behaviour
Should be running
Screenshots
Environment
Additional context