<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Fuse on *scratch*</title>
    <link>https://www.scrivano.org/tags/fuse/</link>
    <description>Recent content in Fuse on *scratch*</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Wed, 18 Nov 2026 15:11:04 +0100</lastBuildDate>
    <atom:link href="https://www.scrivano.org/tags/fuse/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Velarx: a container engine with a chain of trust</title>
      <link>https://www.scrivano.org/posts/2026-11-18-velarx/</link>
      <pubDate>Wed, 18 Nov 2026 10:00:00 +0100</pubDate>
      <guid>https://www.scrivano.org/posts/2026-11-18-velarx/</guid>
      <description>&lt;p&gt;For the last few weeks I&amp;rsquo;ve been working on Velarx, a container engine&#xA;written in Rust that is built around composefs from the start.  I used&#xA;AI heavily to prototype it, otherwise in a few weeks I wouldn&amp;rsquo;t have&#xA;gotten to something that runs real images and that I could compare with&#xA;Podman.  Like composefs, it stores every file by its fs-verity digest.&#xA;The name comes from the Latin &lt;em&gt;velox&lt;/em&gt;, swift, and &lt;em&gt;arx&lt;/em&gt;, citadel, and&#xA;those are the two goals: it has to be fast, and what it runs must be&#xA;verified from the image signature down to every page the kernel reads.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
