https://youtu.be/buY3keP97Jc?si=MbFCEnfp14KNlJvt
YouTubeColin Walters
This demonstrates "logically bound images" with bootc: https://github.com/containers/bootc/issues/128
N@j0rge @M2 might be good for Bluefin-cli?
Jyeah this is for like ucore custom images imo
JI hope he does videos about this regularly though
Alooks like a sysext replacement ngl
NI think that's definitely the target use case.
NI think this is nice though because it's almost like quadlets, but they are tied to the upgrades using bootc.
RI guess there's no difference operationally to updating the digest/version tag inside a quadlet.
It just downloads the update before boot rather than after to improve startup times
It just downloads the update before boot rather than after to improve startup times
A
Amost impressive feature
A
Jwe asked for that!
Jand we got it!
NThe progress bar? Lol
Jyeah
NHopefully we can get it in rpm-ostree
NBased on the conversations I had in the bootc initiative meeting today, we are still quite far away from local layering being a reality in bootc. Which is something Bazzite needs.
NOnce we get that progress bar though, updates from game mode will finally be accurate.
Adepends, the overall progressbar does not have size info, so there will be some skewness
NTrue. We're getting closer though!
Aoh nice bounded images look quite cool
Athe garbage collection
ZYeah I saw you representing Universal Blue there. Very cool stuff. Glad were helping out with that initiative.
I personally am excited for bootc in the cloud/server space. Like you said, until we get layering I dont think bootc will be able to replace rpm-ostree and therefore tough to use for desktops
I personally am excited for bootc in the cloud/server space. Like you said, until we get layering I dont think bootc will be able to replace rpm-ostree and therefore tough to use for desktops
Ai dont think most of our users layer anymore
Zyeah but they can. and i think thats the key. also some of the ujust stuff like sunshine and openzazr layer stuff on top which Bazzite would def need
Athats unfortunate
NThanks! I'm glad you enjoyed the presentation. I'm hopeful there is a future at some point which doesn't require local layering, but that is even farther away more than likely 
K
NLook, y'all merged rechunk faster than I expected. I should've known better.
NLook buddy.
Knah I got you on local layering too now homie
Kunderpromiser
NDid you have to disable SElinux?
NOr did you, Brian, and Lennart fix it? 
Knawww
NThis must be very new.
NI am intrigued and terrified
Ahow do we deal with version drift between sysext and the container image
Ado you remake it as part of the ujust and launch with a systemd service?
Aif you do that'd be very cool
N@Kyle Gospo is lacking in details. Such a tease.
KTBD, we can of course ship them as part of the image so they always match as a way to allow uninstallation of applications by deleting the extension
KBut stuff we aren't going to include by default is going to need some kind of store or updater
KOr, if built locally, will need a service to rebuild as needed
KIt's more or less a new package format
Aim convinced of sysupd and sysext as a packaging format
Ayet
Abut they solved a lot of problems already
NThat's the biggest concern I have. I wonder if maybe building a conversion tool that creates it from an RPM would be potentially a good way to go?
KGet outta my head
