-
Notifications
You must be signed in to change notification settings - Fork 33
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
images: Add Fedora ELN bootc #6168
Conversation
image-refresh fedora-eln-bootc done: https://github.com/cockpit-project/bots/commits/image-refresh-fedora-eln-bootc-20240403-170843 |
osbuild/bootc-image-builder#321 got fixed, so we can get rid of that expensive "local registry" hack 🎉 But starter-kit doesn't work yet, this needs some further adjustments. |
I have a bigger stumbling block: On this image, running cockpit/ws fails:
On our fedora-coreos image, As that seems difficult to work around, and perhaps ELN is a bit too far off "sanity" territory, I'll consider building c9s instead tomorrow. I pushed the (otherwise working) ELN commit as 528f6d9 , so that we get it archived in GitHub for the future. |
This introduces an image which uses [bootc](https://containers.github.io/bootc/) for deploying OCI container images as OS. The initial installation is a bit tricky as it requires converting a container image to a bootable qcow2 image. That happens with https://github.com/osbuild/bootc-image-builder which is very demanding: It needs both /dev/kvm and a `--privileged` container, so the only place where we can run this is in a VM on our own CI. Add manual test map entries for a few projects where we may want to start using this image. https://issues.redhat.com/browse/COCKPIT-1108
Ah, needs to be filed from origin anyway. Closing then, then we have that whole PR as an archive. |
This introduces an image which uses bootc for deploying OCI container images as OS.
The initial installation is a bit tricky as it requires converting a container image to a bootable qcow2 image. That happens with https://github.com/osbuild/bootc-image-builder which is very demanding: It needs both /dev/kvm and a
--privileged
container, so the only place where we can run this is in a VM on our own CI.https://issues.redhat.com/browse/COCKPIT-1108