Malheureusement il renforce le côté "immutable" de #uBlue, car il en bloque tout simplement les mises à jour 🙃 c'est réparable mais quelle tannée.
J'ai étudié et testé CoreOS et je suis tombé dans un rabbit hole 🙈 mais j'ai enfin publié mes 12 notes !
https://notes.sklein.xyz/2025-10-13_2224/
#Fedora #Linux #bootc #libostree #composefs #atomicdesktops #adminsys #fedoracoreos #coreos
The recording of my third talk with Pragyan and Vitaly at All Systems Go! about UKI, composefs and remote attestation for Bootable Containers is now available: https://app.media.ccc.de/v/all-systems-go-2025-362-uki-composefs-and-remote-attestation-for-bootable-containers
#ASG2025 #AllSystemsGo #AllSystemsGo2025 #UKI #composefs #bootc #BootableContainers #RemoteAttestation
With Bootable Containers (bootc), we can place the operating system files inside a standard OCI container. This lets users modify the con...
ARCH LINUX BOOTC WORKS. I DECLARE THE LINUX ATOMIC AGE IS UPON US!
Highlights from the main #erofs (used by #composefs) merge for #Linux 6.17[1]:
""We now support metadata compression. It can be useful for embedded use cases or archiving a large number of small files.
Additionally, readdir performance has been improved by enabling readahead (note that it was already common practice for ext3/4 non-dx and f2fs directories). We may consider further improvements later toalign with ext4's s_inode_readahead_blks behavior for slow devices too.""
[1] https://git.kernel.org/torvalds/c/76a9701325d39d8602695b19c49a9d0828c897ca
We are bringing UKI and strong boot integrity guarantees with composefs to Bootable Containers. We demonstrated our latest progress on that front at DevConf.cz 2025: https://pretalx.devconf.info/devconf-cz-2025/talk/739KGC/
Using composefs and fs-verity, we can link a UKI to a complete read only filesystem tree, guarenteeing that every byte of every file is verified on load. This is done, similar to Git, using only hashes. This means that the signature on the UKI effectively signs the whole tree. With composefs, file content is split from the metadata which enables de-duplication at the file level. We can thus host any number of OS images on a single filesystem and there is no need to reserve space on the system in advance for each image. This frees us from fixed size disk image formats such as dm-verity which is used in a lot of image based systems. We illustrate this architecture by building an OS image using an OCI container via the familiar Containerfile syntax, then pushing it to a container registry and finally deploying it on a system. We will also explain how this will be integrated with the Bootable Containers project (bootc).
Lol @siosm we've got a PR in to fastfetch to fix the disk display thing for #composefs
@abbra Sorry for the late reply, missed your toot.
Is there really no way to create a directory at runtime anymore? Creating and maintaining a container image where the only difference is a symlink seems a little tedious.
I already tried tmpfiles.d, but either I did it wrong or it runs too late in the boot process and the root filesystem is already read-only...
WOW I didn't realize I am already using #Bootc and #ComposeFS on my system.
Thanks #uBlue #AuroraLinux
Now let's check the status of #Podman + ComposeFS...