If using bazzite as a base, installing akmod using the current module will almost likely drift because bazzite move pretty fast. The kernel version in bazzite-41 tag is usually newer than the stable version and can be even newer than testing or unstable. You also can't install akmods if you are using older tag with older kernel version at all. I propose to add kernel version too in akmods template like so.
format!("akmods:{b}-{os_version}-{kernel_version}"),
format!("akmods-extra:{b}-{os_version}-{kernel_version}"),
You can get the kernel version by doing skopeo inspect docker://ghcr.io/ublue-os/bazzite:stable | jq -r '.Labels["ostree.linux"]'. I'm currently doing it using github action before the bluebuild action and using the skip_checkout flag, the kernel version is inserted to github variable and i use the copy module and doing sed on that to dynamically change the kernel version. Also i'm aware of #241 , but i'm not sure how that work or if it will be implemented in near future.
I can help implement it if needed.
If using bazzite as a base, installing akmod using the current module will almost likely drift because bazzite move pretty fast. The kernel version in bazzite-41 tag is usually newer than the stable version and can be even newer than testing or unstable. You also can't install akmods if you are using older tag with older kernel version at all. I propose to add kernel version too in akmods template like so.
You can get the kernel version by doing
skopeo inspect docker://ghcr.io/ublue-os/bazzite:stable | jq -r '.Labels["ostree.linux"]'. I'm currently doing it using github action before the bluebuild action and using the skip_checkout flag, the kernel version is inserted to github variable and i use the copy module and doing sed on that to dynamically change the kernel version. Also i'm aware of #241 , but i'm not sure how that work or if it will be implemented in near future.I can help implement it if needed.