<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Infrastructure on Luther Monson</title>
    <link>https://luth.io/tags/infrastructure/</link>
    <description>Recent content in Infrastructure on Luther Monson</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Wed, 18 Nov 2026 09:00:00 -0700</lastBuildDate>
    <atom:link href="https://luth.io/tags/infrastructure/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Dagger on ephemerd, and a Warm Cache on Throwaway Runners</title>
      <link>https://luth.io/blog/2026/11/dagger-on-ephemerd-runner-fleet/</link>
      <pubDate>Wed, 18 Nov 2026 09:00:00 -0700</pubDate>
      <guid>https://luth.io/blog/2026/11/dagger-on-ephemerd-runner-fleet/</guid>
      <description>&lt;p&gt;A friend asked me whether Dagger replaces ephemerd. It doesn&amp;rsquo;t — they sit at different layers, and I wrote half this post explaining that before I noticed the more interesting question hiding underneath it.&lt;/p&gt;&#xA;&lt;p&gt;Ephemeral runners throw the whole machine away after every job. That is deliberate: a fork PR gets a clean, single-use box and nothing it does survives. But the build cache does not survive either. Every job starts cold — re-pull the base images, recompile from scratch, re-download every dependency. The usual fix is a long-running build engine with a persistent disk, which for a hardened fleet means standing up a privileged box that sits &lt;em&gt;outside&lt;/em&gt; your isolation. That trade bothered me enough to measure the alternative.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
