<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Podman on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/podman/</link>
    <description>Recent content in Podman on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 28 Apr 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/podman/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Docker Compose vs Podman Compose vs Nerdctl: Best Container Compose CLI 2026</title>
      <link>https://www.pistack.xyz/posts/docker-compose-vs-podman-compose-vs-nerdctl-container-compose-tools-2026/</link>
      <pubDate>Tue, 28 Apr 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/docker-compose-vs-podman-compose-vs-nerdctl-container-compose-tools-2026/</guid>
      <description>&lt;h2 id=&#34;why-you-need-a-compose-cli-alternative&#34;&gt;Why You Need a Compose CLI Alternative&lt;/h2&gt;&#xA;&lt;p&gt;Docker Compose is the de facto standard for defining and running multi-container applications. Its YAML-based format — &lt;code&gt;docker-compose.yml&lt;/code&gt; — has become so ubiquitous that entire ecosystems of self-hosted software distribute ready-made compose files. But Docker Compose has a hard dependency: the Docker daemon (&lt;code&gt;dockerd&lt;/code&gt;).&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
