Bhttps://github.com/ublue-os/akmods/pull/394
Note: I want to see the builds look good before I un-draft, but it's promising.
Note: I want to see the builds look good before I un-draft, but it's promising.
Jok what are we thinking support wise?
Jlike I'm not looking for ARM/nvidia builds
JI'm thinking stable/latest for bluefin
BThe most obvious issue seems to be with nivida
JThe only machines I care about in that config are not consumer ones, hence GDX
Bi thought you use NVidia on GDX?
Bok, you don't need nvidai
Bso for CentOS, you don't even need common akmods
Bbut for coreos-stable you do
B(eg bluefin:stable)
Bi kinda think bazzite is going to be a problem with the various kmods
BJright, what I mean to say is bluefin fedora doesn't need any nvidia arm, don't need the builds there
Bbut i will probably make the build work so it's generic and available... since it's uCore will want those drivers too
Jyeah and I don't think we pulled in zfs to gdx either, so this is useful, thanks
Byep
Bwelcome
B.
BOK... good progress on the ARM build PR @M2 and @j0rge
https://github.com/ublue-os/akmods/pull/394
and this run demonstrates that we can build for ARM on some releases (eg F42) but not others (F41) https://github.com/ublue-os/akmods/actions/runs/17482839878?pr=394
and other runs show no ARM builds (bazzite and main) while all the CentOS 10 builds have both ARM and x86_64
https://github.com/ublue-os/akmods/pull/394
and this run demonstrates that we can build for ARM on some releases (eg F42) but not others (F41) https://github.com/ublue-os/akmods/actions/runs/17482839878?pr=394
and other runs show no ARM builds (bazzite and main) while all the CentOS 10 builds have both ARM and x86_64
Ball this is defined by our
images.yaml and workflows generate properly with the Justfile ...Jwe won't need 41 soon
JSorry for the confusion on the PR. I saw aarch64 building in the centoskmodsig CI job so assumed it was running already
Bgotcha
Bno worries
BFor the record I did review your modifications to the Justfile regarding manifest creation and I don’t believe they work as written, though I get the idea of what you were trying to do.
I hope to get back to this late tonight or tomorrow.
I hope to get back to this late tonight or tomorrow.
B@M2 if you have a chance to weigh in you are welcome to contribute to my PR above.
My goals:
Ideally I want to run manifest if either an arm or x86 kernel is cached, but right now the workflow assumes the x86 kernel existing is enough, which is probably adequate.
Beyond that, the Justfile should probably check if the expected image with arch specific tag exists before adding to manifest.
I think we could do that with skopeo, but not podman-manifest or podman-image since those look at local state not remote.
My goals:
Ideally I want to run manifest if either an arm or x86 kernel is cached, but right now the workflow assumes the x86 kernel existing is enough, which is probably adequate.
Beyond that, the Justfile should probably check if the expected image with arch specific tag exists before adding to manifest.
I think we could do that with skopeo, but not podman-manifest or podman-image since those look at local state not remote.
BSo I’ll probably do the latter first, and make a note regarding the former.
Bok!
BGitHub
The good @m2 recently refactored akmods in a most excellent way, and included ready-to-test aarch64 build support.
It's time to give it a try.
It's time to give it a try.
Bi added this to the PR
I'm pretty confident with this PR at this point.
The conditional manifest generation was the last hurdle, but since we use just variables to allow generation of a full script, we can see it should be working quite nicely.
In a nutshell, this enables ARM for akmods builds of:
CentOS kernel
CentOS Kmods SIG kernel
CoreOS kernels
longterm 6.12 fedora kernel
NOT for:
bazzite kernels
"main" (latest fedora) kernels
anything on Fedora 41
the images.yaml format and workflow/justfile support building: x86_64 only, aarch64 only, or both. Currently we have x86_64 only and both building.
When merging, the primary thing to be watching will be that manifests generate correctly as that should be the only thing which impacts current x86_64 builds.
Band I'lm looking for approvals
J... and my axe
J@Kyle Gospo around nerd?
Bi would really like more than 2 approvals... especially would prefer at least a glance over by @M2 given he's the mastermind of the current akmods build structure... though, i think i've done him proud on this one
Jok turn the automerge off
Bi got a second approval.. i'm going to merge
Bugh
Bcentos and centos-kmodsig broke
Band they were both fine a day ago
Bmight be getting rate limited
Jbuilders are saturated too
Jit'll be a hot minute
Byeah, it's fine
Bpicked a bad time to merge i guess
Bbah
Bmanifest stuff doesn't work anyway
Jlooks like the entire project is rebuilding rn
Bdangit, found the mistake for manifest
Bok, i'm going to force merge now
