falcosecurity / test-infra

Falco workflow & testing infrastructure
https://prow.falco.org
Apache License 2.0
31 stars 109 forks source link

Missing falco prebuilt module falco_amazonlinux2_4.14.268-205.500.amzn2.x86_64_1.ko #652

Closed mcbarzi closed 2 years ago

mcbarzi commented 2 years ago

Describe the bug

Missing prebuilt falco module for latest ami

How to reproduce it

Expected behaviour

Screenshots

Environment

Additional context

maxgio92 commented 2 years ago

Hello @mcbarzi , thanks for the opened issue and welcome!

The way the prebuilt drivers are distributed is a best effort way, but you can help us have the coverage as wide as possible. And you can contribute to this repo, by adding a configuration for your Amazon Linux kernel release (i.e. 4.14.268-205.500.amzn2.x8664).

If you see the structure of this repository you'll find a driverkit/config/ folder; in this folder you have one folder per Falco driver version (as a SHA hash).

Inside each of them you have one build configuration per kernel release, and each of them will be consumed by Driverkit, during the CI process.

In your case you'll end up with a config file named _amazonlinux2_4.14.268-205.500.amzn2.x86_641.yaml, with a content like:


kernelversion: 1
kernelrelease: 4.14.268-205.500.amzn2.x86_64
target: amazonlinux2
output:
  module: output/<Falco Driver version>/falco_amazonlinux2_4.14.268-205.500.amzn2.x86_64_1.ko

and if you can do it for each Falco driver version you see under driverkit/config in this repo.

Note: keep in mind that then, the CI (in detail Driverkit) will say if there will be kernel headers available for this kernel release, otherwise it won't be possible to build Falco drivers in the CI.

Feel free to ask and reach out if you need something else :-)

Have a nice day

zuc commented 2 years ago

This is now solved thanks to #654.

/close

poiana commented 2 years ago

@zuc: Closing this issue.

In response to [this](https://github.com/falcosecurity/test-infra/issues/652#issuecomment-1072559337): >This is now solved thanks to #654. > >/close Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.