-
Notifications
You must be signed in to change notification settings - Fork 293
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
EKS version 1.20.4 Not Supported - Getting "Runtime error: error opening device /host/dev/falco0" #234
Comments
I'm getting the same on a new cluster I spun up today running v1.18.9-eks-d1db3c
|
I am facing the same issue with normal local installation using helm in minikube. Below my output from the terminal :- rams3sh@system:~/falco$ helm install falco falcosecurity/falco
NAME: falco
LAST DEPLOYED: Wed Jun 2 13:19:45 2021
NAMESPACE: default
STATUS: deployed
REVISION: 1
TEST SUITE: None
NOTES:
Falco agents are spinning up on each node in your cluster. After a few
seconds, they are going to start monitoring your containers looking for
security issues.
No further action should be required.
Tip:
You can easily forward Falco events to Slack, Kafka, AWS Lambda and more with falcosidekick.
Full list of outputs: https://github.com/falcosecurity/charts/falcosidekick.
You can enable its deployment with `--set falcosidekick.enabled=true` or in your values.yaml.
See: https://github.com/falcosecurity/charts/blob/master/falcosidekick/values.yaml for configuration values.
rams3sh@system:~/falco$ kubectl get pods
NAME READY STATUS RESTARTS AGE
falco-wzww2 0/1 CrashLoopBackOff 1 17s
podwithsa 1/1 Running 23 47d
rams3sh@system:~/falco$ kubectl logs -f falco-wzww2
* Setting up /usr/src links from host
* Running falco-driver-loader for: falco version=0.28.1, driver version=5c0b863ddade7a45568c0ac97d037422c9efb750
* Running falco-driver-loader with: driver=module, compile=yes, download=yes
* Unloading falco module, if present
* Trying to load a system falco module, if present
* Looking for a falco module locally (kernel 5.8.0-53-generic)
* Trying to download a prebuilt falco module from https://download.falco.org/driver/5c0b863ddade7a45568c0ac97d037422c9efb750/falco_ubuntu-generic_5.8.0-53-generic_60.ko
* Download succeeded
insmod: ERROR: could not insert module /root/.falco/falco_ubuntu-generic_5.8.0-53-generic_60.ko: Operation not permitted
Wed Jun 2 07:50:05 2021: Falco version 0.28.1 (driver version 5c0b863ddade7a45568c0ac97d037422c9efb750)
Wed Jun 2 07:50:05 2021: Falco initialized with configuration file /etc/falco/falco.yaml
Wed Jun 2 07:50:05 2021: Loading rules from file /etc/falco/falco_rules.yaml:
Wed Jun 2 07:50:05 2021: Loading rules from file /etc/falco/falco_rules.local.yaml:
Wed Jun 2 07:50:05 2021: Unable to load the driver.
Wed Jun 2 07:50:05 2021: Runtime error: error opening device /host/dev/falco0. Make sure you have root credentials and that the falco module is loaded.. Exiting.
|
hi guys, I get the same error installing with Helm in eks
It was working fine last week following the same steps. Let me know if I can provide any more info or test something. Logs below:
|
I'm facing an identical issue using eks 1.18 version and
|
Getting same error, k3s 1.21.2 + local-path-provisioner It might be invalid url for driver...
|
If you can make changes to the host, I think you can install kernel headers on the host, and falco-driver-loader will build and install the kernel modules. $ k -n falco logs falco-4xfzb
* Setting up /usr/src links from host
* Running falco-driver-loader for: falco version=0.29.1, driver version=17f5df52a7d9ed6bb12d3b1768460def8439936d
* Running falco-driver-loader with: driver=module, compile=yes, download=yes
* Unloading falco module, if present
* Trying to load a system falco module, if present
* Looking for a falco module locally (kernel 5.4.129-62.227.amzn2.x86_64)
* Trying to download a prebuilt falco module from https://download.falco.org/driver/17f5df52a7d9ed6bb12d3b1768460def8439936d/falco_amazonlinux2_5.4.129-62.227.amzn2.x86_64_1.ko
curl: (22) The requested URL returned error: 404
Unable to find a prebuilt falco module
* Trying to dkms install falco module with GCC /usr/bin/gcc
DIRECTIVE: MAKE="'/tmp/falco-dkms-make'"
Kernel preparation unnecessary for this kernel. Skipping...
Building module:
cleaning build area...
'/tmp/falco-dkms-make'....
cleaning build area...
DKMS: build completed.
falco.ko:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/5.4.129-62.227.amzn2.x86_64/kernel/extra/
depmod....
DKMS: install completed.
* falco module installed in dkms, trying to insmod
* Success: falco module found and loaded in dkms
Tue Jul 20 23:21:29 2021: Falco version 0.29.1 (driver version 17f5df52a7d9ed6bb12d3b1768460def8439936d)
Tue Jul 20 23:21:29 2021: Falco initialized with configuration file /etc/falco/falco.yaml
Tue Jul 20 23:21:29 2021: Loading rules from file /etc/falco/falco_rules.yaml:
Tue Jul 20 23:21:30 2021: Loading rules from file /etc/falco/falco_rules.local.yaml:
Tue Jul 20 23:21:30 2021: Starting internal webserver, listening on port 8765 |
Do we have a schedule to update the driver link for AWS Linux kernel? In my case
|
Seeing the same 404 on GKE for https://download.falco.org/driver/17f5df52a7d9ed6bb12d3b1768460def8439936d/falco_cos_5.4.89%2B_1.ko Ah the answer for me is https://falco.org/docs/getting-started/third-party/production/#gke |
For GKE and helm chart what is needed is described here: https://github.com/falcosecurity/charts/tree/master/falco#using-falcosecuritydriver-loader-image-with-ebpf |
Issues go stale after 90d of inactivity. Mark the issue as fresh with Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with Provide feedback via https://github.com/falcosecurity/community. /lifecycle stale |
Any updates on this? We have deployed on EKS 1.20.4 and it is also throwing the 404 error because it cannot find the built driver modules. |
Stale issues rot after 30d of inactivity. Mark the issue as fresh with Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with Provide feedback via https://github.com/falcosecurity/community. /lifecycle rotten |
Rotten issues close after 30d of inactivity. Reopen the issue with Mark the issue as fresh with Provide feedback via https://github.com/falcosecurity/community. |
@poiana: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
The same problem with eks control plane and nodes versions - v1.22.6-eks.
|
EKS version 1.20.4-eks-6b7464
Latest chart version: 0.28.1
Might be related to:
falcosecurity/falco#1078
Thanks
The text was updated successfully, but these errors were encountered: