# container registry Published articles for container registry. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Manage Vercel Container Registry with Vercel CLI DevFeed: [Manage Vercel Container Registry with Vercel CLI]() Original publisher: [Read original article]() Author: Andy Waller Published: 2026-08-20T00:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [Vercel](), [Command-line interface](), [Docker](), [Tooling]() Tags: [buildah](), [cli](), [container-registry](), [docker](), [images](), [podman](), [registry](), [vercel]() ### AI overview Vercel CLI now provides a vcr command group for managing Vercel Container Registry. Developers can connect existing container tools, authenticate with a short-lived project-scoped token, build and push images, create repositories, and inspect repositories, images, and tags. ### Source excerpt You can now manage Vercel Container Registry with Vercel CLI. The new vercel vcr command group lets you: Connect your existing container tooling Build and push images in one step Create and inspect repositories, images, and tags Authenticate your container tooling, such as Docker, Podman, or Buildah, with a short-lived token scoped to your project. Then build and push: The credentials go to Docker itself, so your existing tooling can push to VCR with standard commands: Repositories are created automatically the first time you push, or explicitly with vercel vcr add. From there, you can list what's stored and inspect individual images and tags: Update to the latest Vercel CLI with pnpm i -g vercel@latest and read the Container Registry docs to get started. Read more ## What Is a Container Registry and How to Use One DevFeed: [What Is a Container Registry and How to Use One]() Original publisher: [Read original article]() Author: Pramodh Kumar M Published: 2026-08-10T17:48:35Z Content type: tutorial Language: en Sources: [Kubernetes - KodeKloud Blog | DevOps, Cloud, Kubernetes, AI Tutorials & More]() Topics: [container images](), [content addressed store](), [Docker Hub](), [Dockerfile](), [supply-chain-security]() Tags: [base-images](), [cache](), [ci-cd](), [cloud](), [container-images](), [container-registry](), [containers](), [content-addressed-store](), [cryptographic](), [devops](), [docker](), [docker-hub](), [docker-login](), [docker-pull-rate-limits](), [docker-registry](), [harbor](), [image-manifest](), [image-retention-policy](), [image-scanning](), [image-tags-vs-digests](), [kubernetes](), [private-registry](), [pull-through-cache](), [reproducible-builds](), [security](), [supply-chain-security]() ### AI overview This guide explains how container registries store and distribute container images, emphasizing the distinction between mutable tags and immutable content digests. It also covers pushing, pulling, authentication, Docker Hub rate limits, caching, scanning, and retention. ### Source excerpt A tag is a bookmark somebody else can move. A digest is the image itself. Once that distinction lands, reproducible builds, supply chain security, and every it worked yesterday mystery make sense. ## Vercel Container Registry repositories can now be made public DevFeed: [Vercel Container Registry repositories can now be made public]() Original publisher: [Read original article]() Author: Luke Phillips-Sheard Published: 2026-08-07T17:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [Vercel](), [Command-line interface](), [REST API]() Tags: [api](), [cli](), [container-registry](), [documentation](), [images](), [registry](), [rest](), [rest-api](), [sandbox](), [update](), [vercel]() ### AI overview Vercel Container Registry repositories can now be made public. Public repositories allow any Vercel team to pull and use their images while retaining read-only access; repositories remain private by default. ### Source excerpt Vercel Container Registry now lets you make a repository public, so anyone with a Vercel account can pull and use its images. Sharing already granted read access to up to 100 teams, and making a repository public opens that access to every Vercel team rather than a named set. Public access is read-only, so anyone can pull and use the images but cannot push, delete, or otherwise change the repository. Repositories stay private by default. Make a repository public from the project dashboard under Images -> repository -> Settings -> Public Access, where confirming requires typing the repository name. You can also set visibility from the Vercel CLI: Public images work like shared images in Vercel Sandbox, which accepts a team-scoped image reference in Sandbox.create(): Update your repository visibility from the dashboard, the CLI, or the REST API, and see the Vercel Container Registry documentation to learn more. Read more ## Share Vercel Container Registry repositories across teams DevFeed: [Share Vercel Container Registry repositories across teams]() Original publisher: [Read original article]() Author: Andy Waller Published: 2026-08-03T00:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [Vercel](), [Command-line interface](), [Authorization]() Tags: [cli](), [container-registry](), [images](), [npm](), [registry](), [vercel]() ### AI overview Vercel Container Registry now supports sharing repositories across Vercel teams with read-only access to all images. Recipients can pull and use images but cannot push, delete, or re-share them. ### Source excerpt Vercel Container Registry now lets you share a repository with other Vercel teams to grant read access to its images. Sharing is read-only and covers the whole repository. Recipients can pull and use every image, but cannot push, delete, or re-share. You can also share a repository with your own team. Each repository can be shared with up to 100 teams. Share from the project dashboard under Images -> repository -> Settings -> Repository Sharing, or with the Vercel CLI: # Share a repository with a team vercel vcr permissions my-repository add other-team # List teams with access vercel vcr permissions my-repository ls # Revoke a team's access vercel vcr permissions my-repository rm other-team # Remove all shared access vercel vcr permissions my-repository clear Shared images can be used in Vercel Sandbox, accepting a team-scoped image reference in Sandbox.create() : import { Sandbox } from '@vercel/sandbox'; const sandbox = await Sandbox.create({ image: 'other-team/their-project/shared-repository:latest', }); Repository sharing is available on all plans. Update the Vercel CLI to v58.3.0 or later with npm i -g vercel@latest to get started and see the Vercel Container Registry documentation to learn more. Read more ## What's new in Graph Artifacts DevFeed: [What's new in Graph Artifacts]() Original publisher: [Read original article]() Author: Zack Warnimont Published: 2026-07-27T09:00:00Z Content type: release Language: en Sources: [Apollo Blog]() Topics: [GraphOS](), [Platform API](), [Deployment](), [Command-line interface](), [Containers](), [CI/CD]() Tags: [announcement](), [api](), [apis](), [ci-cd](), [cli](), [container-registry](), [deployment](), [graphos](), [oci](), [registry](), [release](), [router]() ### AI overview This release adds GraphOS artifact tag management across Rover and Studio. Teams can assign, list, fetch, and delete tags from Rover, view tags alongside artifact digests in Studio, and use OCI-compliant registry APIs. User-managed tags support promotion and rollback workflows, while tag reassignment hot-reloads automatically on Router v2.11.0 and later. ### Source excerpt When we launched Graph Artifacts, we gave teams a way to pin their GraphOS Router to a specific, immutable supergraph schema version using SHA digests. Graph artifacts are stored using OCI-compliant registries, and tagging is a native concept at that layer. A tag is just a mutable pointer to an immutable digest. In principle, nothing stopped a team from tagging an artifact prod and having their router resolve it. ## Bring your Dockerfile to Vercel Functions DevFeed: [Bring your Dockerfile to Vercel Functions]() Original publisher: [Read original article]() Author: Joe Haddad Published: 2026-06-30T00:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [Vercel](), [Dockerfile](), [Containers](), [Docker]() Tags: [autoscaling](), [container-images](), [container-registry](), [containers](), [docker](), [docker-containers](), [oci](), [routing](), [vercel]() ### AI overview Vercel Functions now support deploying HTTP servers from Dockerfile or Containerfile projects using OCI-compatible container images on Fluid compute. Images are built, pushed to Vercel Container Registry, and deployed on each commit, while retaining Vercel preview deployments, logs, routing, and autoscaling benefits. ### Source excerpt Vercel Functions now support deploying HTTP servers from a Dockerfile or Containerfile, using Open Container Initiative (OCI) compatible images on Fluid compute. This makes it easier to bring existing applications written in any language to Vercel while keeping the preview deployments, logs, routing, and autoscaling benefits of using Vercel Functions and Fluid compute. To use container images with your functions, create a project with a Dockerfile.vercel (or Containerfile.vercel) file that starts an HTTP server listening on $PORT: This image will be built, pushed, and deployed on every commit to Vercel Container Registry. Learn more about using container images in the docs and see seven ways you can use Docker containers on Vercel. Read more ## Vercel Sandbox now support Custom Images DevFeed: [Vercel Sandbox now support Custom Images]() Original publisher: [Read original article]() Author: Tom Lienard Published: 2026-06-30T00:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [Vercel](), [toolchain](), [Docker](), [boot]() Tags: [boot](), [compute](), [container-registry](), [dependencies](), [docker](), [documentation](), [filesystem](), [images](), [os](), [performance](), [registry](), [sandbox](), [sandboxes](), [snapshots](), [toolchain](), [vercel]() ### AI overview Vercel Sandboxes now support custom images in public beta. Users can provide a custom root filesystem with their own operating system, toolchain, and dependencies. Images are pulled from Vercel Container Registry, and the feature is designed to preserve cold start performance through precompiled snapshots. ### Source excerpt Vercel Sandboxes now supports custom images. Launching in public beta today, images allow Sandboxes to start with your own custom root filesystem. Images are pulled from Vercel Container Registry, so anything you docker push is immediately available. Bring your own OS, toolchain and dependencies into the Sandbox without needing to spin up compute and create Snapshots. Images in the background for Fluid Compute and boot from a precompiled snapshot in the same format as our Sandbox Snapshots - so you get the convenience of a custom filesystem without sacrificing cold start performance. Read more about running images with Sandbox in the documentation. Read more ## Introducing VCR: Vercel Container Registry DevFeed: [Introducing VCR: Vercel Container Registry]() Original publisher: [Read original article]() Author: Wilson Wang Published: 2026-06-30T00:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [Vercel](), [Dockerfile](), [Containers](), [Authorization](), [OpenID connect (OIDC)](), [dashboards]() Tags: [authorization](), [container-images](), [container-registry](), [docker](), [infrastructure](), [oci](), [oidc](), [operations](), [registry](), [vercel](), [workflows]() ### AI overview Vercel introduces Vercel Container Registry, an OCI-compliant registry for pushing, pulling, and managing container images through standard Docker workflows. It supports project-scoped authorization, OIDC or access-token authentication, automatic optimization for Sandboxes and Functions, and integration with Vercel build and deployment workflows. ### Source excerpt You can now push, pull, and manage container images directly on Vercel. Vercel Container Registry is an OCI-compliant image registry hosted on Vercel infrastructure. It works with standard workflows like docker push, docker pull, and docker tag, so there's nothing new to learn or tooling to migrate. A Vercel project can have unlimited repositories. You can create and manage them through the Vercel dashboard, or push directly to VCR, which creates the repository for you on the fly. Operations use the same authorization controls as the rest of Vercel. You can authenticate with OIDC or an access token, provided the token has access to the project scope. Optimized for Fluid Compute When you push an image, VCR automatically optimizes it in the background for use in Sandboxes and Functions. VCR stores a precompiled snapshot and serves that snapshot when the image is requested. These snapshots use the same format as Sandbox Snapshots, which are optimized to run on Fluid Compute. Build and deploy on Vercel The Vercel build environment is automatically set up with authentication for the current project, so you can build and store images as part of the build and deploy process. You can also bring your Dockerfile to Vercel directly and host it with Vercel Functions or Vercel Sandboxes. Read more about VCR in the documentation. Read more ## Six Live Kubernetes Recommendations: AKS, Cilium, Rate Limiting, and More DevFeed: [Six Live Kubernetes Recommendations: AKS, Cilium, Rate Limiting, and More]() Original publisher: [Read original article]() Author: Adam Gordon Bell Published: 2026-06-15T12:00:00Z Content type: tutorial Language: en Sources: [Pulumi]() Topics: [Kubernetes](), [Azure](), [C#](), [Cilium](), [Docker Hub](), [Web app]() Tags: [ai-coding](), [aks](), [azure](), [c-sharp](), [cilium](), [container-registry](), [dotnet](), [kubernetes](), [tutorials](), [web-app]() ### AI overview A writeup of a live workshop on building an AKS cluster, Azure Container Registry, and a random-cat web app in C# with Pulumi. It presents recommendations for working with Kubernetes on Azure, including choosing a language the team already uses, and describes how Docker Hub rate limiting affected the workshop. ### Source excerpt On June 10th, Engin and I ran a live workshop building an AKS cluster, an Azure Container Registry, and a random-cat web app from scratch in C#. This is the writeup, including the parts we didn't get to live. Since this post was published, Pulumi has added first-class support for HashiCorp Configuration Language (HCL). You can now write Pulumi programs in HCL directly, alongside general-purpose languages like TypeScript, Python, Go, and C#. To see how it works, see Pulumi HCL. Live demos keep you honest. On June 10th my AKS workshop went a little sideways. Partway through, Docker Hub rate-limited my image pull and we had to adapt the content on the fly. The original plan was to stand up an AKS cluster with Cilium, an Azure Container Registry with the cluster's pull permission wired in code, and a random-cat web app, then split the infrastructure from the workload into separate Pulumi stacks. Live, we didn't make it through all of that, but we had some fun tangents and it turned out to be a great session. So here are my six recommendations for working with Kubernetes on Azure from this recent workshop. 1. Pick the language your team already uses I opened the session by asking the room what language they prefer to work in, with one caveat from me: "Hopefully, it's not PowerShell because this is not in PowerShell." We got some C# answers and zero requests for PowerShell, which works out, because the whole workshop is in PowerShell C#. I chose C# because, first, I genuinely love the language. I spent the early part of my career as a C# developer, and on Azure it just makes sense. Second, an Azure workshop tends to draw a big turnout of C# devs, and if they aren't C# devs themselves, they often work somewhere the backend team uses C#. Pulumi lets you bring that language to your infrastructure rather than learn a new DSL. AI coding assistants also came up. LLMs have substantially more C# and Go in their training data than HCL or Bicep. As I put it live: "If you're working ## New Chainguard Images July-September 2024: Hardened, minimal containers DevFeed: [New Chainguard Images July-September 2024: Hardened, minimal containers]() Original publisher: [Read original article]() Published: 2024-10-03T00:00:00Z Content type: release Language: en Sources: [Chainguard: Unchained]() Topics: [chainguard images](), [releases](), [Containers](), [GitLab](), [Amazon Elastic Kubernetes Service](), [PyTorch]() Tags: [amazon-eks](), [chainguard](), [chainguard-images](), [container-images](), [container-registry](), [containers](), [gitlab](), [images-directory](), [kubernetes](), [pytorch](), [releases]() ### AI overview Chainguard reports approximately 192 new hardened, minimal images released from July through September 2024, including FIPS-enabled images and images for GitLab, Amazon EKS, and PyTorch. ### Source excerpt Check out Chainguard's new image releases over summer 2024, including container images for GitLab, Amazon EKS, and PyTorch applications. ## Chainguard Images now available on Magalu Cloud container registry DevFeed: [Chainguard Images now available on Magalu Cloud container registry]() Original publisher: [Read original article]() Published: 2023-12-12T00:00:00Z Content type: news Language: en Sources: [Chainguard: Unchained]() Topics: [chainguard images](), [container images](), [Cloud](), [Kubernetes](), [supply-chain-security]() Tags: [brazil](), [chainguard](), [chainguard-images](), [container-registry](), [cve](), [kubernetes](), [magalu](), [security](), [software-supply-chain-security]() ### AI overview Chainguard Images are now available through Magalu Cloud's container registry and Kubernetes as a service in Brazil. The article highlights hardened Chainguard Developer Images, which are updated daily and patched against CVEs by default, along with commercially supported Production Images for enterprise and compliance requirements. ### Source excerpt Chainguard Developer Images arrive on Magalu Cloud, Brazil's growing digital ecosystem, ensuring hardened, CVE-patched Kubernetes service. ## How to use multiple Docker registry mirrors DevFeed: [How to use multiple Docker registry mirrors]() Original publisher: [Read original article]() Author: Alex Ellis Published: 2023-06-08T13:27:06Z Content type: tutorial Language: en Sources: [Alex Ellis' Blog]() Topics: [Docker](), [docker registry](), [pull through cache](), [Self-hosted](), [GitHub Actions](), [Firecracker]() Tags: [buildx](), [cache](), [container](), [container-registry](), [docker](), [docker-registry](), [firecracker](), [github-actions](), [how-to](), [kubernetes](), [linux](), [mirror](), [registries](), [registry](), [self-hosted]() ### AI overview This tutorial explains why self-hosted GitHub Actions runners can hit Docker Hub's anonymous image pull limits and how a Docker registry configured as a pull-through cache can help. It covers configuring Docker and buildx to use multiple registry mirrors, including considerations for local HTTP and Internet-facing HTTPS setups. ### Source excerpt Why would you need to use a mirror for a container registry? And is there a way to use two or more? Find out from the actuated team. ## Deploy and Handle GCP CloudTasks with Goblet in minutes. DevFeed: [Deploy and Handle GCP CloudTasks with Goblet in minutes.]() Original publisher: [Read original article]() Author: Mauricio Wittenberg Published: 2023-04-18T13:55:58Z Content type: tutorial Language: en Sources: [Engineering at Premise - Medium]() Topics: [Google Cloud Platform (GCP)](), [Python](), [Microservices](), [Serverless](), [IAM](), [Architecture & Design](), [Docker](), [Docker Image]() Tags: [cloud-computing](), [cloud-tasks](), [cloudrun](), [container-registry](), [docker](), [docker-image](), [gcp](), [goblet](), [google-cloud](), [google-cloud-platform](), [iam](), [infrastructure](), [microservices](), [permissions](), [python](), [rate-limiting](), [serverless](), [tutorial]() ### AI overview This tutorial explains how Goblet can deploy and manage Google Cloud Tasks for serverless microservices on Google Cloud Platform. It covers defining a queue, enqueuing and handling tasks in Python, configuring IAM permissions, and deploying related infrastructure, Docker images, and Cloud Run revisions. ### Source excerpt by Mauricio Wittenberg. Goblet DeployIntroduction CloudTasks is a Google Cloud Platform (GCP) service that allows users to enqueue tasks in a queue. It is somewhat similar to PubSub, but with CloudTasks, the queue has features such as rateLimits and retryConfig. This can be very useful when having to enforce a rate limit over an external API or retrying tasks that have a known probability of failure. If you want to use CloudTasks you will have to manually deploy cloud infrastructure, understand the CloudTask object, deal with client libraries and figure out multiple IAM role bindings. Or you can use Goblet for all the heavy lifting and in just a few minutes be able push a task and later process the task in a Python function of our choosing. Goblet is a Python based cloud framework for building serverless microservices on Google Cloud Platform. It enables developers to quickly and reliably deploy cloud resources together with the code that will make use of those resources. In this blog post we will review how Goblet deploys CloudTaskQueues and provides the user with an simple code interface to enqueue and handle CloudTasks⁶. Using the short snipped of code below we can define a queue, create a client, push a task to the queue, and handle tasks from the queue! https://medium.com/media/d81fb2d8bd47a3f69479708d61dd5230/href See the rest of the tutorial for setting up your Goblet environment, setting permissions, and deploying you infrastructure and application in a few quick steps. Infrastructure For this tutorial we will use an example GCP project called goblet-cloudtask and deploy region specific resources to us-central1. If you would like to follow along the complete code can be found at gcp-tutorials. The account used to run this example must have enough IAM role binding to run all the gcloud commands described in the Set-Up section below. Now, let's take a look at the infrastructure Goblet will create. We won't have to take care of any of these steps ourselves. All ## Publish a Docker container from Bitbucket to Google Cloud Container Registry DevFeed: [Publish a Docker container from Bitbucket to Google Cloud Container Registry]() Original publisher: [Read original article]() Published: 2019-08-07T00:00:00Z Content type: tutorial Language: en Sources: [Juri Strumpflohner]() Topics: [Docker](), [bitbucket](), [Google Cloud Platform (GCP)](), [Docker Hub](), [Automation](), [Git](), [Jenkins](), [GitLab]() Tags: [automation](), [bitbucket](), [circleci](), [container-registry](), [docker](), [git](), [gitlab](), [google-cloud](), [jenkins](), [registry]() ### AI overview This tutorial explains how to configure a Bitbucket pipeline to automatically build and publish Docker container images to a private repository in Google Cloud Container Registry. It covers triggering builds from commits and Git tags, setting required environment variables, authenticating with Google Cloud, and tagging images. ### Source excerpt Lorem ipsum dolor sit amet ## How Shopify Governs Containers at Scale with Grafeas and Kritis DevFeed: [How Shopify Governs Containers at Scale with Grafeas and Kritis]() Original publisher: [Read original article]() Author: Jonathan jonathan pulsifer com Published: 2017-10-12T15:02:00Z Content type: article Language: en Sources: [Shopify Engineering](), [Shopify Engineering - Shopify Engineering]() Topics: [Containers](), [Shopify](), [supply-chain-security](), [Google](), [Kubernetes](), [ci](), [Open Source](), [Security]() Tags: [attestation](), [audits](), [ci](), [container-registry](), [containers](), [deployment](), [google](), [identity](), [images](), [kubernetes](), [open-source](), [operations](), [packages](), [pipelines](), [policy](), [production](), [registry](), [security](), [shopify](), [software-supply-chain]() ### AI overview Shopify describes using Google's open source Grafeas to centralize metadata about container builds, images, packages, origins, deployments, and vulnerabilities. It also uses Kritis with Kubernetes to enforce real-time deployment policies based on signed attestations generated during CI. ### Source excerpt Today, Google and its contributors launched Grafeas, an open source initiative to define a uniform way for auditing and governing the modern software supply chain. At Shopify, we're excited to be part of this announcement. Grafeas, or "scribe" in Greek, enables us to store critical software component metadata during our build and integration pipelines.