Khad to adjust slightly based on build
NDone
Kthank
JGitHub
For the upcoming Fedora 41 release, we are enabling composefs by default for bootable container images of Fedora Atomic Desktops (not for the classic ostree ones). See: https://fedoraproject.org/wi...
MHi. Where i can find URL's for such repos to other tools? For example, I need to install XOW for my Bazzite, because my xbox controller won't connect properly. So i need to install libusb package
Ai iven made a presentation for today lmao
Avery professional
KGitHub
Matches a change in akmods at ublue-os/akmods#230
Kneed 2 more acks for this
R
Rand two reviews on https://github.com/ublue-os/ucore/pull/187
A@Noel the meeting is in one hour and change right?
AIf you want we can start the call half an hour before
N1.5 hours yeah.
NSure! Let's that. @Kyle Gospo
N@uBlue Members @Bazzite Contributor I just got off a call for the bootc initiative and if we want bootc enabled by default in Fedora 41, we need more folks to try and help with some issues to push things over the finish line. There are a set of tasks regarding bootupd and composefs. bootupd issues need to be tackled first since composefs issues depends on them, followed by the composefs issues. Here is a link to each of the issues that @Timothée Ravier has laid out:
Tuesday, 14:00 UTC
You can join the meeting at https://meet.google.com/poh-xmxm-qyc
- bootupd: https://gitlab.com/fedora/ostree/sig/-/issues/1#note_2062751164
- composefs: https://gitlab.com/fedora/ostree/sig/-/issues/35#note_2062769940
Tuesday, 14:00 UTC
You can join the meeting at https://meet.google.com/poh-xmxm-qyc
GitLab
Fedora Atomic systems (rpm-ostree based systems) do not update the BIOS / EFI bootloaders files by default on updates as this operation may fail and leave the system...
GitLab
Composefs is the next step toward better integrity guarantees on Atomic Desktops. We want to enable it for Fedora Atomic...
K@Noel is layering working on bootc yet?
AWe should try composefs
Nyou mean local layering?
KYeah
Bi dont think layering on client side is in plan for bootc at least every time i read it wasnt
Kdnf is supposed to provide it client side eventually
AIt is
ECan take a closer look later today but this sounds interesting and would love to help get things over the line
RIt is planned, but to start with, will just forward requests to rpm-ostree
KBut I don't think we can support it until that happens
KAt least not in Bazzite
Nnot to my knowledge no. The meeting you Antheas and I are having is to discuss rechunk with Red Hat.
AActivating a usroverlay might be a way to get fast layering
Nwe can. rpm-ostree and bootc can run side by side.
Nif any local layering is happening, it just needs to be done through rpm-ostree.
Bthats new then
KThat's doable today, but from that point on bootc can't do anything.
Nright, bootc would be vestigial until we can build the images using it and DNF features catch up.
Nit at least would be there.
KI feel like that complicates our updater then, I almost rather just not ship it until it's ready
Ntopgrade doesn't support bootc anyway.
NEither way, I'm not pushing us to use bootc right away in Bazzite, I'm more so trying to see if we can get some help upstream to make this stuff move along more quickly.
RThe idea is the RedHat folks need help working on the issues Noel shared so they can start tackling the more important things like local layering. It seems like there's a lack of headcount available
RAt the moment, they are working on bringing the existing images (FCOS, Atomic Desktops etc) as closely inline with the bootc base images as possible, without rebasing on the bootc images, hence the composefs changes
AWhat does the image have to do with composefs
GBefore we switch images to composefs we'll need to remove bind mounts
AWhat bind mounta
RBootc requires composefs (i believe).
Current atomic desktop images do not use composefs.
They are trying to make the atomic desktop images to look as much like bootc images as possible to minimize the number of changes when the final switch happens
Current atomic desktop images do not use composefs.
They are trying to make the atomic desktop images to look as much like bootc images as possible to minimize the number of changes when the final switch happens
GGitHub
Bazzite is a custom image built upon Fedora Atomic Desktops that brings the best of Linux gaming to all of your devices - including your favorite handheld. - ublue-os/bazzite
NI could be wrong on this, but composefs isn't required for bootc, it's more a nice to have? They want it for it's ability to help verify files on disk
GThis is just one of them
GThere's a couple others in bluefin and bazzite
RIt's enabled in the base image builds
https://gitlab.com/fedora/bootc/base-images/-/blob/main/tier-0/ostree.yaml#L13-14
https://gitlab.com/fedora/bootc/base-images/-/blob/main/tier-0/ostree.yaml#L13-14
