https://deploy-preview-3174--ornate-narwhal-088216.netlify.app/tags/registry/Recent content in Registry onHugo -- gohugo.ioen-USTue, 31 Mar 2026 00:00:00 +0000https://deploy-preview-3174--ornate-narwhal-088216.netlify.app/chainguard/chainguard-images/chainguard-registry/pull-through-guides/artifact-registry-pull-through/Mon, 08 Jul 2024 15:56:52 -0700https://deploy-preview-3174--ornate-narwhal-088216.netlify.app/chainguard/chainguard-images/chainguard-registry/pull-through-guides/artifact-registry-pull-through/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 Chainguard’s registry. This mirror can then serve as a pull through cache for your Chainguard Containers. This tutorial outlines how to set up a remote repository with Google Artifact Registry.https://deploy-preview-3174--ornate-narwhal-088216.netlify.app/chainguard/chainguard-images/chainguard-registry/overview/Tue, 21 Mar 2023 16:36:47 +0000https://deploy-preview-3174--ornate-narwhal-088216.netlify.app/chainguard/chainguard-images/chainguard-registry/overview/Chainguard Registry hosts more secure container images with two access tiers: public Free images available to everyone, and production images that require authentication for enterprise features like SLAs and version pinning. The registry integrates with standard container tools while providing enhanced security through signed images and comprehensive metadata. While all public Chainguard Containers are freely available, logging in with a Chainguard account and authenticating when pulling from the registry provides a mechanism for Chainguard to contact you if there are any current or known upcoming issues with images you are pulling.https://deploy-preview-3174--ornate-narwhal-088216.netlify.app/chainguard/chainguard-images/chainguard-registry/pull-through-guides/ecr-pull-through/Tue, 31 Mar 2026 00:00:00 +0000https://deploy-preview-3174--ornate-narwhal-088216.netlify.app/chainguard/chainguard-images/chainguard-registry/pull-through-guides/ecr-pull-through/In March 2026, AWS announced support for using Amazon Elastic Container Registry (ECR) as a pull-through cache for Chainguard’s registry. This means you can configure ECR to automatically cache Chainguard container images, reducing your dependency on Chainguard’s registry for production workloads. For setup and configuration instructions, refer to the official AWS documentation: Amazon ECR pull through cache rules Pulling an image with a pull through cache rule Learn More You can review our Registry Overview to learn more about Chainguard’s registry, or check out our Containers documentation to learn more about Chainguard Containers.https://deploy-preview-3174--ornate-narwhal-088216.netlify.app/chainguard/chainguard-images/chainguard-registry/authenticating/Tue, 21 Mar 2023 15:10:16 +0000https://deploy-preview-3174--ornate-narwhal-088216.netlify.app/chainguard/chainguard-images/chainguard-registry/authenticating/Public Container Images Chainguard offers a collection of images that are publicly available, don’t require authentication, and are free to use by anyone. However, logging in with a Chainguard account and authenticating when pulling from the registry gives you access to the Chainguard Console, and provides a mechanism for Chainguard to contact you if there are any issues with images you are pulling. This may enable Chainguard to notify you of upcoming deprecations, changes in behavior, critical vulnerabilities and remediations for images you have recently pulled.