<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Mirroring on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/mirroring/</link>
    <description>Recent content in Mirroring on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 17 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/mirroring/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted Container Registry Mirroring: Docker Registry Mirror vs Harbor vs Nexus Repository</title>
      <link>https://www.pistack.xyz/posts/2026-05-17-container-registry-mirroring-docker-harbor-nexus-guide/</link>
      <pubDate>Sun, 17 May 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-05-17-container-registry-mirroring-docker-harbor-nexus-guide/</guid>
      <description>&lt;p&gt;Container registry mirroring is a critical capability for organizations that need to cache Docker images locally, reduce external bandwidth costs, and maintain operational resilience when public registries are unavailable. This guide compares three self-hosted solutions for container registry mirroring: Docker Registry (mirror/proxy mode), Harbor (CNCF graduated), and Sonatype Nexus Repository OSS.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
