Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: use kernel version as tags in akmod #354

Open
asen23 opened this issue Feb 7, 2025 · 2 comments
Open

feat: use kernel version as tags in akmod #354

asen23 opened this issue Feb 7, 2025 · 2 comments
Assignees
Labels
priority: critical Should be done as soon as possible type: bug Something isn't working. upstream Issue should be filed upstream, or was caused by / is waiting an upstream change

Comments

@asen23
Copy link

asen23 commented Feb 7, 2025

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.

@porkloin
Copy link

porkloin commented Feb 7, 2025

👋 Just wanted to say I'm also interested in this feature, since I have a need to grab a specifically tagged kernel version.

@gmpinder gmpinder self-assigned this Feb 7, 2025
@gmpinder gmpinder added type: bug Something isn't working. priority: critical Should be done as soon as possible upstream Issue should be filed upstream, or was caused by / is waiting an upstream change labels Feb 7, 2025
@gmpinder
Copy link
Member

Might be related to #241

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: critical Should be done as soon as possible type: bug Something isn't working. upstream Issue should be filed upstream, or was caused by / is waiting an upstream change
Projects
None yet
Development

No branches or pull requests

3 participants