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
AIf it takes 20s off the update size
AI'm up for it
AQueue the 200 proton bugs
AAfter rechunk this shouldn't be rewuired
APlz check gamescope has the correct perms
ACaps
AAt least it has the cap before it enters rechunk
AAnd every other file with caps works after rechunk
NI'd be curious if it still works even without composefs
Nwhat I was told by Dan Walsh was composefs is primarily used with a feature in the kernel to verify files on the disk to ensure they have not changed.
GI think bootc works without yes
GWe had it for a period of time on uBlue images
NOK, that's what I figured.
AYeah it enables verity on the base image
ASo the whole image is signed
Nit was. I'm not sure what happened there. @M2 and I enabled it and then we had to disable it for some reason. Then I kinda went on hiatus for a bit.
AThe iso broke
RGuys I installed bazzite os gnome on my msi claw and my controls and not working
Noh, that's a bug we should file with @Skynet then. bootc should work.
ANice, open a help thread plz
GDoes the composefs changes also change us to UKI?
AWe can't use uki with secure boot
AWell with Ms secure boot
AIf some of you want to enroll your own keys you can use uki
GOh yeah that's right lol because Microsoft only wants to sign a shim
AUsers have to sign their ukis
RGuys help
AThe infra for producing ukis that can adapt to devices is not there yet
AAt least for bazzite
APerhaps it's there for bluefin
AWith ukis you have to sign all kernel parameters
AAny user will use
AAnd the users can't change them afterwards
GHow could I test this in a custom image?
AUh have fun reading the systemd uki docs
AI only know what you have to do in theory
AIf secure boot is on the uki ignores the kernel parameters you pass to it
AAnd you have to make uki extensions that get conditionally loaded based on the device to change the kernel params
GDoes ostree/silverblue even support booting them?
SWhat's a bug? The tests I run on my repo use a bootc image. If they're passing, then you should be able to install a bootc image since installing is one of the tests
NYeah, I feel like I need to do some new testing as I feel like we aren't operating on current info.
APerhaps not generating them yet
