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

Build ebpf objects from a standardised container #1243

Closed
rafaelroquetto opened this issue Oct 9, 2024 · 1 comment · Fixed by #1639 or #1666
Closed

Build ebpf objects from a standardised container #1243

rafaelroquetto opened this issue Oct 9, 2024 · 1 comment · Fixed by #1639 or #1666
Assignees

Comments

@rafaelroquetto
Copy link
Contributor

Use a container featuring a standard toolchain to build our ebpf binaries. Quoting cilium/ebpf docs:

We recommend building eBPF C code from within a container with a stable LLVM toolchain, as well as checking all generated .o and .go files into source control. This buys you fully-reproducible builds, prevents bugs due to team members using different LLVM versions and makes your packages fully independent and go runnable. It also prevents PII from leaking into ELFs in the form of absolute paths to .c source files in DWARF info.

@mariomac
Copy link
Contributor

We already have the generator.Dockerfile that already generates that image. It is shipped here: https://github.com/grafana/beyla/pkgs/container/beyla-generator

To build the eBPF artifacts from it, just use: make docker-generate

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