<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Dind on Luther Monson</title>
    <link>https://luth.io/tags/dind/</link>
    <description>Recent content in Dind on Luther Monson</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Sat, 24 Oct 2026 10:00:00 -0700</lastBuildDate>
    <atom:link href="https://luth.io/tags/dind/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Docker-in-Docker in CI Without Handing Jobs Root</title>
      <link>https://luth.io/blog/2026/10/docker-in-docker-without-root/</link>
      <pubDate>Sat, 24 Oct 2026 10:00:00 -0700</pubDate>
      <guid>https://luth.io/blog/2026/10/docker-in-docker-without-root/</guid>
      <description>&lt;p&gt;&lt;a href=&#34;https://luth.io/blog/2026/08/ephemerd-one-daemon-every-os/&#34;&gt;ephemerd&lt;/a&gt; runs a fresh GitHub Actions runner per job. Some of those&#xA;jobs need Docker. A workflow builds an image, runs a service container, or uses the &lt;code&gt;container:&lt;/code&gt; key. The usual way to&#xA;give a self-hosted job Docker is Docker-in-Docker, or dind.&lt;/p&gt;&#xA;&lt;p&gt;The catch is what dind normally costs you. The standard recipe is a &lt;code&gt;--privileged&lt;/code&gt; container. Privileged hands the job&#xA;most of root on the host. For CI that runs fork pull requests, that is a non-starter. A fork PR is a stranger&amp;rsquo;s code.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
