Unable to build kernel module for Ubuntu AWS with 5.11.x kernels (GLIBC_2.33)
LucaGuerra opened this issue · 4 comments
Describe the bug
Some recent images require a version of GLIBC that is newer than the one shipped with our standard build image. To fix this, we may need to use different Docker images to build different kernels.
How to reproduce it
Try building this image: https://github.com/falcosecurity/test-infra/blob/master/driverkit/config/17f5df52a7d9ed6bb12d3b1768460def8439936d/ubuntu-aws_5.11.0-1008-aws_8.yaml
./driverkit docker -c config/3aa7a83bf7b9e6229a3824e3fd1f4452d1e95cb4/ubuntu-aws_5.11.0-1008-aws_8.yaml --driverversion 3aa7a83bf7b9e6229a3824e3fd1f4452d1e95cb4 --timeout 1000 -l debug
DEBU + make KERNELDIR=/tmp/kernel-download/usr/src/linux-headers-5.11.0-1008-aws
DEBU Ymake -C /tmp/kernel-download/usr/src/linux-headers-5.11.0-1008-aws M=/tmp/driver modules
DEBU Ymake[1]: Entering directory '/tmp/kernel-download/usr/src/linux-headers-5.11.0-1008-aws'
DEBU CC [M] /tmp/driver/main.o
DEBU �scripts/basic/fixdep: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by scripts/basic/fixdep)
DEBU make[2]: *** [scripts/Makefile.build:287: /tmp/driver/main.o] Error 1
DEBU make[2]: *** Deleting file '/tmp/driver/main.o'
DEBU 2make[1]: *** [Makefile:1848: /tmp/driver] Error 2
DEBU Xmake[1]: Leaving directory '/tmp/kernel-download/usr/src/linux-headers-5.11.0-1008-aws'
DEBU $make: *** [Makefile:7: all] Error 2
DEBU log pipe close error=EOF
DEBU context canceled
FATA exiting error="Error: No such container:path: 1a4c2eba0899548dab4a773a7e5bb925bc0b1bebab491f5412d15cb102967bbf:/tmp/driver/module.ko"
Expected behaviour
The kernel module builds correctly.
Screenshots
Environment
- Falco version:
0.30.0 - System info:
- Cloud provider or hardware configuration:
- OS:
- Kernel:
- Installation method:
docker
Additional context
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
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle rotten
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Provide feedback via https://github.com/falcosecurity/community.
/close
@poiana: Closing this issue.
In response to this:
Rotten issues close after 30d of inactivity.
Reopen the issue with
/reopen.Mark the issue as fresh with
/remove-lifecycle rotten.Provide feedback via https://github.com/falcosecurity/community.
/close
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.