Newshot
Account

Vercel Container Registry now supports 2 GB compressed image layers

Summary

Vercel Container Registry now supports compressed image layers of up to 2 GB each, up from 500 MB, the total image size limit stays 15 GB. The registry works with standard workflows like docker push , docker pull , and docker tag , and pushing an image creates the repository on the fly. Repositories can be made public for read-only pull access by any Vercel team, or shared with specific teams up to 100 from the dashboard or with vercel vcr permissions . The Vercel Managed Images that Vercel Sandbox runs on are served from ordinary public repositories, built with the same public-repository feature any team can use for its own images. Manage repositories, images, and tags with the vercel vcr CLI commands in Vercel CLI v58.3.0 or later, and log CI workflows in from GitHub Actions with the vercel/vcr-action/login action using GitHub OIDC, which removes the need for long-lived registry credentials. If background optimization of a pushed image fails, the image shows an error status in the da…

Original text(via Vercel Blog)

Vercel Container Registry now supports compressed image layers of up to 2 GB each, up from 500 MB, the total image size limit stays 15 GB.

The registry works with standard workflows like docker push, docker pull, and docker tag, and pushing an image creates the repository on the fly.


        docker buildx build --push -t vcr.vercel.com/team/project/repository:tag .
      

Repositories can be made public for read-only pull access by any Vercel team, or shared with specific teams up to 100 from the dashboard or with vercel vcr permissions. The Vercel Managed Images that Vercel Sandbox runs on are served from ordinary public repositories, built with the same public-repository feature any team can use for its own images.

Manage repositories, images, and tags with the vercel vcr CLI commands in Vercel CLI v58.3.0 or later, and log CI workflows in from GitHub Actions with the vercel/vcr-action/login action using GitHub OIDC, which removes the need for long-lived registry credentials. If background optimization of a pushed image fails, the image shows an error status in the dashboard, and pushing the same image again retries the conversion.

See the documentation for the full setup.

The text above was extracted automatically from the source page and may miss images, tables or code blocks. The original is authoritative.

Published by Vercel Blog
This site only summarises and aggregates; copyright stays with the original author. Headlines and summaries follow the source — where they differ, the original wins.
Read the original ↗