Skip to content
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

Falco Unable to insmod module on Amazon Linux 2 EKS #3102

Open
rama-akbar opened this issue Feb 20, 2024 · 8 comments
Open

Falco Unable to insmod module on Amazon Linux 2 EKS #3102

rama-akbar opened this issue Feb 20, 2024 · 8 comments

Comments

@rama-akbar
Copy link

Describe the bug

We want to install Falco into our EKS cluster, but got an Unable to insmod module error.

Expected behaviour

Falco running sucess

Error Message

2024-02-19 12:26:52 INFO  Running falcoctl driver install
                      ├ driver version: 7.0.0+driver
                      ├ driver type: kmod
                      ├ driver name: falco
                      ├ compile: true
                      ├ download: true
                      ├ arch: x86_64
                      ├ kernel release: 5.10.198-187.748.amzn2.x86_64
                      └ kernel version: #1 SMP Tue Oct 24 19:49:54 UTC 2023
2024-02-19 12:26:52 INFO  Found distro target: amazonlinux2
2024-02-19 12:26:52 INFO  Check if kernel module is still loaded.
2024-02-19 12:26:52 INFO  OK! There is no module loaded.
2024-02-19 12:26:52 INFO  Check all versions of kernel module in dkms.
2024-02-19 12:26:52 INFO  OK! There are no module versions in dkms.
2024-02-19 12:26:52 INFO  Trying to download a driver.
                      └ url: https://download.falco.org/driver/7.0.0%2Bdriver/x86_64/falco_amazonlinux2_5.10.198-187.748.amzn2.x86_64_1.ko
2024-02-19 12:26:54 INFO  Driver downloaded.
                      └ path: /root/.falco/7.0.0+driver/x86_64/falco_amazonlinux2_5.10.198-187.748.amzn2.x86_64_1.ko
2024-02-19 12:26:54 WARN  Unable to insmod module.
                      ├ driver: /root/.falco/7.0.0+driver/x86_64/falco_amazonlinux2_5.10.198-187.748.amzn2.x86_64_1.ko
                      └ err: exit status 1

Environment

  • Falco version:
    falcosecurity/falco-no-driver:0.37.1
    falcosecurity/falco-driver-loader:0.37.1
    falcosecurity/falcoctl:0.7.2

  • System info:

  • Cloud provider or hardware configuration: AWS (EKS)

  • OS:
    Amazon Linux 2

  • Kernel:
    kernel release: 5.10.198-187.748.amzn2.x86_64
    kernel version: Digwatch compiler #1 SMP Tue Oct 24 19:49:54 UTC 2023

  • Installation method:
    Helm Chart

@FedeDP
Copy link
Contributor

FedeDP commented Feb 20, 2024

Hi! Thanks for opening this issue! Can you manually try insmod /root/.falco/7.0.0+driver/x86_64/falco_amazonlinux2_5.10.198-187.748.amzn2.x86_64_1.ko and paste here the output?

@FedeDP
Copy link
Contributor

FedeDP commented Feb 20, 2024

/assign

@rama-akbar
Copy link
Author

@FedeDP

Output of insmod, we deploy it using helm chart from official falco - https://github.com/falcosecurity/charts/blob/master/charts/falco/values.yaml

insmod: ERROR: could not insert module root/falco_amazonlinux2_5.10.198-187.748.amzn2.x86_64_1.ko: Operation not permitted

@FedeDP
Copy link
Contributor

FedeDP commented Feb 23, 2024

Mmh it seems like you are missing some permissions; how did you deploy the Falco helm chart? Did you modify anything from default values?

@rama-akbar
Copy link
Author

Hi @FedeDP
here is diff

left = ours
right = current chart https://github.com/falcosecurity/charts/blob/master/charts/falco/values.yaml

https://www.diffchecker.com/HPWzTzsU/


Is there posibility latest version of falco didn't support on Amazon Linux 2 ?

@FedeDP
Copy link
Contributor

FedeDP commented Feb 26, 2024

Mmmh from your diff, it seems like you are using ebpf driver?

kind: ebpf
ebpf:
path:

But why did you clear up the path? Also, your OP showed that falcoctl tried to install kmod instead (and indeed the error is about insmod).

Is there posibility latest version of falco didn't support on Amazon Linux 2 ?

Nope, we support amazonlinux2.

@rama-akbar
Copy link
Author

Mmmh from your diff, it seems like you are using ebpf driver?

kind: ebpf
ebpf:
path:

But why did you clear up the path? Also, your OP showed that falcoctl tried to install kmod instead (and indeed the error is about insmod).

I'm not sure actually, because chart we used is chart when we deploy falco version 0.34.1, if we deploy falco 0.34.1 it works fine.

but when we deploy latest version 0.37.1, we getting the kernel module issue

@poiana
Copy link

poiana commented May 26, 2024

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants