<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Registry on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/registry/</link>
    <description>Recent content in Registry on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 24 Apr 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/registry/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Docker Registry Proxy Cache: Distribution vs Harbor vs Zot 2026</title>
      <link>https://www.pistack.xyz/posts/2026-04-24-docker-registry-proxy-cache-distribution-harbor-zot-guide/</link>
      <pubDate>Fri, 24 Apr 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-04-24-docker-registry-proxy-cache-distribution-harbor-zot-guide/</guid>
      <description>&lt;p&gt;If you run Docker containers across multiple hosts or CI/CD pipelines, pulling images from Docker Hub repeatedly is wasteful. You hit &lt;a href=&#34;https://docs.docker.com/docker-hub/download-rate-limit/&#34;&gt;rate limits&lt;/a&gt;, waste bandwidth, and slow down deployments. A self-hosted Docker registry proxy cache solves all three problems.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
