<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Pull-through guides on</title><link>https://edu.chainguard.dev/chainguard/containers/registry/pull-through-guides/</link><description>Recent content in Pull-through guides on</description><generator>Hugo -- gohugo.io</generator><language>en-US</language><copyright>Copyright (c) 2023 Chainguard</copyright><lastBuildDate>Tue, 09 Jul 2024 08:49:15 +0000</lastBuildDate><atom:link href="https://edu.chainguard.dev/chainguard/containers/registry/pull-through-guides/index.xml" rel="self" type="application/rss+xml"/><item><title>How to set up pull through from Chainguard's registry to Amazon ECR</title><link>https://edu.chainguard.dev/chainguard/containers/registry/pull-through-guides/ecr-pull-through/</link><pubDate>Tue, 31 Mar 2026 00:00:00 +0000</pubDate><guid>https://edu.chainguard.dev/chainguard/containers/registry/pull-through-guides/ecr-pull-through/</guid><description>&lt;p&gt;In March 2026, AWS &lt;a href="https://aws.amazon.com/about-aws/whats-new/2026/03/amazon-ecr-pull-through-cache-chainguard/"&gt;announced support&lt;/a&gt; for using Amazon Elastic Container Registry (ECR) as a pull through cache for Chainguard&amp;rsquo;s registry. By configuring a pull through cache rule, you can pull Chainguard Containers through your own ECR private registry. ECR caches each image on the first pull and checks the upstream registry for a newer version at most once every 24 hours, which reduces your workloads&amp;rsquo; direct dependency on Chainguard&amp;rsquo;s registry.&lt;/p&gt;</description></item><item><title>How to set up pull-through from Chainguard's container registry to Artifactory</title><link>https://edu.chainguard.dev/chainguard/containers/registry/pull-through-guides/artifactory-containers-pull-through/</link><pubDate>Tue, 13 Feb 2024 15:56:52 -0700</pubDate><guid>https://edu.chainguard.dev/chainguard/containers/registry/pull-through-guides/artifactory-containers-pull-through/</guid><description>&lt;p&gt;Organizations can route container image pulls through Artifactory to centralize artifact management, enforce policy, and integrate Chainguard Containers into existing CI/CD workflows. You can configure Artifactory as a pull-through cache by setting up a remote repository pointed at &lt;a href="https://edu.chainguard.dev/chainguard/chainguard-registry/overview/"&gt;Chainguard&amp;rsquo;s container registry&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;This tutorial outlines how to set up remote repositories with &lt;a href="https://jfrog.com/artifactory/"&gt;JFrog Artifactory&lt;/a&gt;. Specifically, it goes over how to set up one repository you can use as a pull-through cache for Chainguard&amp;rsquo;s public &lt;a href="https://edu.chainguard.dev/chainguard/containers/concepts/container-categories/#free-containers"&gt;Free containers&lt;/a&gt; and another you can use for &lt;a href="https://edu.chainguard.dev/chainguard/containers/concepts/container-categories/#production-containers"&gt;Production containers&lt;/a&gt; originating from a private Chainguard repository. It also outlines how you can use one of Artifactory&amp;rsquo;s &lt;a href="https://jfrog.com/help/r/jfrog-artifactory-documentation/virtual-repositories"&gt;virtual repositories&lt;/a&gt; as a pull-through cache to access resources from multiple remote repositories in a single location.&lt;/p&gt;</description></item><item><title>How to pull packages from Chainguard package repositories through Artifactory</title><link>https://edu.chainguard.dev/chainguard/containers/registry/pull-through-guides/artifactory-packages-pull-through/</link><pubDate>Thu, 14 Nov 2024 15:56:52 -0700</pubDate><guid>https://edu.chainguard.dev/chainguard/containers/registry/pull-through-guides/artifactory-packages-pull-through/</guid><description>&lt;p&gt;This tutorial details how to set up remote Alpine package (apk) repositories with &lt;a href="https://jfrog.com/artifactory/"&gt;JFrog Artifactory&lt;/a&gt;, which can provide pull-through caches for Chainguard package repositories. Specifically, this guide walks you through how to set up remote Artifactory repositories to serve as pull-through caches for a &lt;a href="https://edu.chainguard.dev/chainguard/containers/building-and-modifying/packages/private-apk-repos/"&gt;Chainguard private APK repository&lt;/a&gt; as well as Chainguard&amp;rsquo;s public package repositories. The guide also outlines how to configure a container image build to pull APK packages from these remote repositories using tokens generated by Artifactory.&lt;/p&gt;</description></item><item><title>How to set up pull through from Chainguard's registry to Cloudsmith</title><link>https://edu.chainguard.dev/chainguard/containers/registry/pull-through-guides/cloudsmith-pull-through/</link><pubDate>Tue, 16 Jul 2024 15:56:52 -0700</pubDate><guid>https://edu.chainguard.dev/chainguard/containers/registry/pull-through-guides/cloudsmith-pull-through/</guid><description>&lt;p&gt;Organizations often have their own internal software repositories and registries integrated into their systems. This guide explains how to set up the Cloudsmith artifact repository to ingest &lt;a href="https://edu.chainguard.dev/chainguard/containers/overview/"&gt;Chainguard Containers&lt;/a&gt; by acting as a pull-through cache.&lt;/p&gt;
&lt;p&gt;This tutorial outlines how to set up a remote repository with &lt;a href="https://cloudsmith.com/"&gt;Cloudsmith&lt;/a&gt;. It will walk you through how to set up a Cloudsmith repository you can use as a pull through cache for Chainguard&amp;rsquo;s Free containers or for Production containers originating from a private Chainguard repository.&lt;/p&gt;</description></item><item><title>How to set up pull through from Chainguard's registry to Google Artifact Registry</title><link>https://edu.chainguard.dev/chainguard/containers/registry/pull-through-guides/artifact-registry-pull-through/</link><pubDate>Mon, 08 Jul 2024 15:56:52 -0700</pubDate><guid>https://edu.chainguard.dev/chainguard/containers/registry/pull-through-guides/artifact-registry-pull-through/</guid><description>&lt;p&gt;Organizations can use Chainguard Containers along with third-party software repositories in order to integrate with current workflows as the single source of truth for software artifacts. In this situation, you can set up a proxy repository to function as a mirror of &lt;a href="https://edu.chainguard.dev/chainguard/chainguard-registry/overview/"&gt;Chainguard&amp;rsquo;s registry&lt;/a&gt;. This mirror can then serve as a pull through cache for your Chainguard Containers.&lt;/p&gt;
&lt;p&gt;This tutorial outlines how to set up a remote repository with &lt;a href="https://cloud.google.com/artifact-registry/docs/repositories/remote-overview"&gt;Google Artifact Registry&lt;/a&gt;. It will walk you through how to set up an Artifact Registry Repository you can use as a pull through cache for Chainguard&amp;rsquo;s Free containers or Production containers originating from a private Chainguard repository.&lt;/p&gt;</description></item><item><title>How to sync images from Chainguard's registry to Harbor</title><link>https://edu.chainguard.dev/chainguard/containers/registry/pull-through-guides/harbor/</link><pubDate>Tue, 19 Aug 2025 12:00:00 +0000</pubDate><guid>https://edu.chainguard.dev/chainguard/containers/registry/pull-through-guides/harbor/</guid><description>&lt;p&gt;&lt;a href="https://goharbor.io"&gt;Harbor&lt;/a&gt; is an open-source artifact registry. It&amp;rsquo;s designed to securely store, manage, and distribute OCI artifacts, including container images and Helm charts by enforcing policies like vulnerability scanning, image signing, and role-based access control. Harbor delivers enterprise-grade compliance, performance, and interoperability across platforms like Kubernetes and Docker, all accessible via a web UI or RESTful API.&lt;/p&gt;
&lt;p&gt;This tutorial outlines how to sync images from Chainguard&amp;rsquo;s registry to a Harbor instance. It describes two approaches:&lt;/p&gt;</description></item><item><title>How to set up pull through from Chainguard's registry to Nexus</title><link>https://edu.chainguard.dev/chainguard/containers/registry/pull-through-guides/nexus-pull-through/</link><pubDate>Thu, 28 Mar 2024 15:56:52 -0700</pubDate><guid>https://edu.chainguard.dev/chainguard/containers/registry/pull-through-guides/nexus-pull-through/</guid><description>&lt;p&gt;Organizations can use Chainguard Containers along with third-party software repositories in order to integrate with current workflows as the single source of truth for software artifacts. In this situation, you can set up a proxy repository to function as a mirror of &lt;a href="https://edu.chainguard.dev/chainguard/chainguard-registry/overview/"&gt;Chainguard&amp;rsquo;s registry&lt;/a&gt;. This mirror can then serve as a pull through cache for your Chainguard Containers.&lt;/p&gt;
&lt;p&gt;This tutorial outlines how to set up a repository with &lt;a href="https://www.sonatype.com/products/sonatype-nexus-repository"&gt;Sonatype Nexus&lt;/a&gt;. Specifically, it will walk you through how to set up one repository you can use as a pull through cache for Chainguard&amp;rsquo;s Free containers or for Production containers originating from a private Chainguard repository.&lt;/p&gt;</description></item></channel></rss>