CI: always build ARM64 images - #95
Conversation
|
Looks like there's a reason this filter was in place, but I agree it's not clear why things are the way they are in many parts of this build pipeline. Apparently there's no zlib/libelf available in the 5.10 cross-compile context. Not sure how that's possible. @florianl would you be able to figure it out? |
|
Looks like arm64 versions of libelf and zlib need to be installed due to torvalds/linux@e96f2d64c812. This is no longer required as of 5.18+. I'll try the build locally and push some patches. |
These still build libbpf for bpf_preload_umd and require those specific ARM64 dependencies to be installed. Signed-off-by: Timo Beckers <timo@isovalent.com>
With a8de719 the Linux kernel versions were updated and the 7.1 tag moved from 7.1.1 to 7.1.12. This change was noticed, as in our CIs 7.1 is used for testing against amd64 and arm64 Linux kernel. But with the mentioned commit, no 7.1.12 arm64 image was created and our CI started to fail. To fix this, always build an arm64 image and don't limit it to static tags. Signed-off-by: Florian Lehner <florianl@users.noreply.github.com>
2460caa to
d1a11bd
Compare
|
@ti-mo sorry for responsing just now. I started looking into it but wanted to do more testing bevore sharing something. |
|
@florianl This should already be fixed and working, arm64 images are built for all supported kernel versions. |
|
ah 🙈 I didn't see the update. Thanks for fixing it! |
With a8de719 the Linux kernel versions were updated and the 7.1 tag moved from 7.1.1 to 7.1.12.
This change was noticed, as in our CIs 7.1 is used for testing against amd64 and arm64 Linux kernel. But with the mentioned commit, no 7.1.12 arm64 image was created and our CI started to fail.
To fix this, always build an arm64 image and don't limit it to static tags.
Reproducer that shows that no arm64 image was created for 7.1.12