<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Ostree on Le Site de François</title><link>https://lesitedefrancois.be/en/tags/ostree/</link><description>Recent content in Ostree on Le Site de François</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>© 2026 François</copyright><atom:link href="https://lesitedefrancois.be/en/tags/ostree/index.xml" rel="self" type="application/rss+xml"/><item><title>bootc (Bootable Containers)</title><link>https://lesitedefrancois.be/en/security/bootc/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://lesitedefrancois.be/en/security/bootc/</guid><description>&lt;p&gt;&lt;strong&gt;bootc&lt;/strong&gt; is a CNCF sandbox project, created by Colin Walters, that applies the OCI container model to operating system delivery. Where conventional container images package an application to run inside a host OS, a bootc image packages the entire OS — kernel (under &lt;code&gt;/usr/lib/modules&lt;/code&gt;), initrd, systemd units, firmware, and all userspace — as a standard &lt;strong&gt;OCI&lt;/strong&gt; image that can be built with &lt;code&gt;podman build&lt;/code&gt; or &lt;code&gt;buildah&lt;/code&gt;, stored in any OCI-conformant registry, signed with standard supply chain tools, and pulled to a machine where it becomes the running system. At runtime the base OS is not running inside a container; systemd is pid 1 as usual. The container image format is purely a transport and build model, not an execution model.&lt;/p&gt;</description></item><item><title>composefs</title><link>https://lesitedefrancois.be/en/security/composefs/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://lesitedefrancois.be/en/security/composefs/</guid><description>&lt;p&gt;&lt;strong&gt;composefs&lt;/strong&gt; is a Linux filesystem technology created by Alexander Larsson and Giuseppe Scrivano at Red Hat that provides cryptographically verified, read-only filesystem trees with opportunistic file-level sharing across images. Its motivating problem is a gap that neither &lt;strong&gt;dm-verity&lt;/strong&gt; nor plain &lt;strong&gt;overlayfs&lt;/strong&gt; fills cleanly: dm-verity provides strong integrity over a whole block device but requires a self-contained disk image and cannot share files between images; overlayfs allows layered, shared filesystems but protects only file contents (via &lt;strong&gt;fs-verity&lt;/strong&gt;) and not the directory structure or metadata — an attacker who can manipulate a file&amp;rsquo;s name, permissions, or position in the tree is not caught. composefs closes that gap by separately protecting content and metadata, then composing them at mount time.&lt;/p&gt;</description></item></channel></rss>