Best way to build with custom kernel

[liyimeng]

I wanna build a variant with my own custom kernel. I make a possibilities exploration, as far as I found, there are some options:

• In Dockerfile.kairos-* add a custom repo, point to rebuild kernel packages.
• Create a luet kernel package in https://github.com/kairos-io/packages reference it in kairos build

I am not sure what is the better way to go, any suggestion?

Thanks a lot in advanced!

[mauromorales]

@liyimeng if you use Ubuntu LTS, you can build your own image with the Kernel you want and feed it as BASE_IMAGE to the Dockerfile.kairos-ubuntu, then we will not install the kernel. For all other distros you will need to do that process yourself. IMO is better to do it in the Dockerfile because you still need to run dracut to build the initramfs at the end of the process, so it cannot be a static package comming for Luet only.

https://github.com/kairos-io/kairos/blob/master/images/Dockerfile.kairos-ubuntu#L166-L167

[mauromorales]

cool let me know if it works. I should have also pointed out to the docs, but I haven't tested the example in the docs recently so keep an eye open there. (the previous example I shared I tested last week so that should work)

https://kairos.io/docs/reference/build-from-scratch/

[liyimeng]

@mauromorales I have test it and confirm it works as you described. However, I get nohang service keep spinning up and down, eating hard of my CPU resource. I have 4G RAM. and free command report no memory issue.

likely be another unknown issue.

[mauromorales]

yeah this might be related to the issue you mentioned on the other comment. When building the kernel, at the end of your Dockerfile, you might be able to disable nohang and see how that works for you. Maybe even completely remove the package

[mauromorales]

the method is still valid. You are building an image with the kernel or any other package that you need. Kernel is just a bit special in that you need to build the initrd afterwards but other than that is just building a new container image and then producing an iso (or any other artifact) with it

[liyimeng]

@mauromorales sorry, my fault, I look at the wrong branch, which contains old code

[liyimeng]

Likely be this one #2195