<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Compose on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/compose/</link>
    <description>Recent content in Compose on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 19 Nov 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/compose/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Docker Compose Hardening in 2026: 20 Settings That Separate a Homelab From Production</title>
      <link>https://www.pistack.xyz/posts/2026-11-19-docker-compose-hardening-checklist-2026/</link>
      <pubDate>Thu, 19 Nov 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-11-19-docker-compose-hardening-checklist-2026/</guid>
      <description>&lt;p&gt;A default &lt;code&gt;docker-compose.yml&lt;/code&gt; is a development artifact. It runs the container as root, gives it the full Linux capability set, mounts writable volumes, writes logs until the disk fills, and declares no health condition at all. That is fine on a laptop for an afternoon. On a server that runs unattended for three years, it is a blueprint for a 100% disk, a privilege-escalation path, and a service that &amp;ldquo;started&amp;rdquo; while its database was still initializing.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
