I have only tested the kernel-install integration feature using bootc images, but it could probably be applicable to other image mode systems that can be built using derived container images. I don’t know if/how it can be used with traditional OSTree systems. Would you mind sharing what commands you tried, the system variant you tried, and the errors returned?
I rebased to the unsigned image, but the kernel install is still not working
rpm-ostree status
State: idle
warning: Failed to query journal: couldn't find current boot in journal
Deployments:
â—Ź ostree-unverified-registry:quay.io/fedora-ostree-desktops/kinoite:41
I tried replacing my kernel with the longterm 6.12 one:
run0
journalctl -t 'rpm-ostree(kernel-longterm-core.posttrans)'
Feb 26 12:23:34 PC rpm-ostree(kernel-longterm-core.posttrans)[23952]: error: rpm-ostree kernel-install wrapper: Datei oder Verzeichnis nicht gefunden (os error 2)
-- Boot 9bb07e16afd840fca8f38ce72de9c536 --
Feb 27 10:17:26 PC rpm-ostree(kernel-longterm-core.posttrans)[377361]: error: rpm-ostree kernel-install wrapper: Datei oder Verzeichnis nicht gefunden (os error 2)
Feb 27 11:26:15 PC rpm-ostree(kernel-longterm-core.posttrans)[427841]: error: rpm-ostree kernel-install wrapper: Datei oder Verzeichnis nicht gefunden (os error 2)
-- Boot cf4b468cdee24d5195aa7ede69f237d7 --
Feb 27 22:37:39 PC rpm-ostree(kernel-longterm-core.posttrans)[33233]: error: rpm-ostree kernel-install wrapper: Datei oder Verzeichnis nicht gefunden (os error 2)
Feb 27 22:40:17 PC rpm-ostree(kernel-longterm-core.posttrans)[36816]: error: rpm-ostree kernel-install wrapper: Datei oder Verzeichnis nicht gefunden (os error 2)
I don’t know about the COPR repo, but the instructions don’t seem quite right. The command from the other related topic should also work for bootable container images.
However, in my humble opinion, the proper way to replace the kernel in these images is to make derived container images, i.e. what is described and tested in the topic you mentioned in your initial post.
While I really appreciate what the folks at the Universal Blue project are doing, I prefer to build my images using the docs and tools already provided by the Fedora and CentOS Stream communities. Through use and testing, I participate in improving the docs and tools on which the Universal Blue project relies. When there is a question or issue here on the forum regarding the Universal Blue project images, I try to help mostly with the uCore images.
I’ve already set up a GitHub peros that builds custom container images based on bootc and the still unofficial Atomic Desktops, and then pushes them daily to quay.io. It’s easy, at least for me, to generate an ISO disk image from these customized container images. So I’m not familiar with the BlueBuild project and don’t know what would cause an issue.