-
Notifications
You must be signed in to change notification settings - Fork 897
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error opening device /host/dev/falco0 #1390
Comments
Hello @alterEgo123, the issue here is that the prebuilt Falco driver (version As stated in the relative proposal we provide prebuilt Falco drivers in a best-effort way. So, we usually ship the prebuilt drivers for the last 2 stable versions of Falco. Turns out you have two options here:
More docs available at: |
@leodido Why only keep the prebuilt drivers for the last 2 stable versions? |
Hi! I am having this similar issue on newer Ubuntu GCP kernels and CentOS 8 kernels - 5.4.0-1025-gcp, 4.18.0-193.6.3.el8 and the drivers are not available here I am installing Falco in a container, so ideally, I'd like Falco to build the kernel module on the fly so my automation does not break(i confirmed that I have kernel-headers installed). Another question - whats the purpose of |
Describe the bug
Hello,
I've been using Falco for a while now as daemonset, and I sometimes get the same issue which is down below. I should also note that it is recurrent for me that I use the same script for installing falco in different K8S clusters, and this issue sometimes arises. I always found that changing the Falco version to be a solution, but I consider this to be an issue because I'm using a fixed version (currently using 0.23.0), and I need to change into newer versions for it to be fixed.
How to reproduce it
kubectl apply -f k8s-with-rbac/falco-daemonset-configmap.yaml (I specify the version 0.23.0)
Expected behaviour
Run falco as daemonset.
Environment
Additional context
The text was updated successfully, but these errors were encountered: