@stefanleh , sorry it took me a while to get back to you here! This one is a bit weird because (to the best of my knowledge) the Fedora docker image will always only have the latest kernel ... so you're correct like 99% of the time and this is the one place where my lazy regex is appropriate enough 😆

What I was really trying to do here was shove the build of this into GitHub Actions but I didn't read the docs first. The linux runners hosted by GitHub have 14 GB disk space and that's nowhere near enough to compile the kernel. I'm still trying to think if I want to keep this code and eventually host something a bit more substantial myself or just revert it. Am super open to feedback here ... and if you'd like to help review any future PRs, I'd ❤️ all the help I can get!

Hi @some-natalie , you are totally correct, for a moment i forgot that we are in the latest fedora image when building the kernel. As i use an intel NIC in SRIOV mode i need the ACS patch myself as the virtual NICs dont get own IOMMU groups. Therefore i build my own docker image: https://github.com/stefanleh/fedora_acs_kernel_build, which needs the version as input parameter. I thought about setting up CI in my own hardware for building the kernels but then how to share them? So maybe it would be wise to have a look at the COPR infrastructure (https://copr.fedorainfracloud.org/)? Then it would be very easy for the folks to use the kernels. Best regards, Stefan

@stefanleh , you're totally right on using COPR instead of GitHub here. I definitely don't have the bandwidth to learn a new CI system at the moment though and was hoping this could be good enough. Let me make investigating COPR into an issue and hopefully I could get to it soon. If you beat me to it, mind sending any links or other things that helped you out my way?

Issue created here - #5