Yandex Cloud
Search
Discuss with expertTry it for free
  • Customer Stories
  • Documentation
  • Blog
  • All Services
    • Cloud Interconnect
    • Cloud Backup
    • Cloud Registry
    • Yandex AI Studio
    • Compute Cloud
    • Object Storage
    • Managed Service for Kubernetes®
    • Yandex BareMetal
    • Smart Web Security
    • Security Deck
    • Managed Service for PostgreSQL
    • Managed Service for ClickHouse®
    • Monium
    • Cloud CDN
    • Network Load Balancer
    • Virtual Private Cloud
    • Cloud DNS
    • Application Load Balancer
    • Yandex Cloud Video
    • Stackland
    • Yandex Cloud Router
    • Yandex Managed Service for Trino
    • Managed Service for MySQL®
    • Managed Service for Valkey™
    • Managed Service for Apache Spark™
    • Yandex StoreDoc
    • Managed Service for OpenSearch
    • Managed Service for Apache Kafka®
    • Data Transfer
    • Yandex MPP Analytics Engine for PostgreSQL
    • Yandex Managed Service for Apache Airflow®
    • Data Processing
    • Yandex MetaData Hub
    • Managed Service for YDB
    • Managed Service for Sharded PostgreSQL
    • Managed Service for YTsaurus
    • Yandex WebSQL
    • DataLens
    • Yandex Search API
    • SpeechSense
    • SpeechKit
    • DataSphere
    • Vision OCR
    • Translate
    • Yandex Identity Hub
    • Key Management Service
    • Certificate Manager
    • Yandex Lockbox
    • Audit Trails
    • SmartCaptcha
    • Cloud Desktop
    • SourceCraft Code Assistant
    • Container Registry
    • Managed Service for GitLab
    • Managed Service for Prometheus®
    • Cloud Functions
    • API Gateway
    • Yandex Cloud Postbox
    • Message Queue
    • Serverless Integrations
    • IoT Core
    • Data Streams
    • Serverless Containers
    • Cloud Notification Service
    • Yandex Query
    • Identity and Access Management
    • Yandex Cloud Console
    • Resource Manager
    • Yandex Cloud Billing
    • Yandex Cloud Quota Manager
    • Cloud Apps
  • System Status
  • Marketplace
    • Featured
    • Infrastructure & Network
    • Data Platform
    • AI for business
    • Security
    • DevOps tools
    • Serverless
    • Monitoring & Resources
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Start testing with double trial credits
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Center for Technologies and Society
    • Yandex Cloud Partner program
    • Price calculator
    • Pricing plans
  • Customer Stories
  • Documentation
  • Blog
© 2026 Direct Cursus Technology L.L.C.
Yandex Container Registry
  • Getting started
    • All guides
    • Installing and configuring Docker
    • Authentication in Container Registry
      • Getting information about existing registries
      • Getting information about a registry access policy
      • Creating a registry
      • Configuring access to a registry
      • Updating a registry
      • Deleting a registry
    • Scanning Docker images for vulnerabilities
    • Creating a trigger for a registry
  • Yandex Container Solution
  • Access management
  • Pricing policy
  • Terraform reference
  • Monitoring metrics
  • Audit Trails events
  • Troubleshooting
  • FAQ
  1. Step-by-step guides
  2. Managing a registry
  3. Creating a registry

Creating a registry

Written by
Yandex Cloud
Improved by
Danila N.
Updated at August 3, 2026
View in Markdown

A new registry can be used by all users and service accounts with access permissions for the folder.

You can create a secure registry with autoscanning using a vulnerability scanner.

Note

Scanning Docker images for vulnerabilities is charged.

Management console
CLI
Terraform
API
  1. In the management console, select the folder where you want to create your registry.

  2. Navigate to Container Registry.

  3. Click Create registry.

  4. Name the registry. The naming requirements are as follows:

    • Length: between 3 and 63 characters.
    • It can only contain lowercase Latin letters, numbers, and hyphens.
    • It must start with a letter and cannot end with a hyphen.
  5. Optionally, under Automatic scanning:

    • Disable Scan Docker images on push to prevent Docker images from being scanned when pushed to the repository.

    • Disable Scan all Docker images in the registry or set the scanning frequency.

      Warning

      Automatic Docker image scanning makes your registry more secure. The default vulnerability scan settings are consistent with the Yandex Cloud cloud infrastructure security standard.

  6. Optionally, add labels.

  7. Click Create registry.

If you do not have the Yandex Cloud CLI yet, install and initialize it.

The folder used by default is the one specified when creating the CLI profile. To change the default folder, use the yc config set folder-id <folder_ID> command. You can also specify a different folder for any command using --folder-name or --folder-id. If you access a resource by its name, the search will be limited to the default folder. If you access a resource by its ID, the search will be global, i.e., through all folders based on access permissions.

  1. Make sure the folder does not contain a registry yet:

    yc container registry list
    

    Result:

    +----+------+-----------+
    | ID | NAME | FOLDER ID |
    +----+------+-----------+
    +----+------+-----------+
    

    If the folder already contains a registry, see Updating a registry for info on how you can update it.

  2. Create a registry:

    • With automated vulnerability scanning:

      yc container registry create --name my-reg --secure
      

      Warning

      Automatic Docker image scanning makes your registry more secure. The default vulnerability scan settings are consistent with the Yandex Cloud cloud infrastructure security standard.

    • Without automated vulnerability scanning:

      yc container registry create --name my-reg
      

    Result:

    done
    id: crpd50616s9a********
    folder_id: b1g88tflru0e********
    name: my-reg
    status: ACTIVE
    created_at: "2019-01-09T14:34:06.601Z"
    

    Follow these registry naming requirements:

    • Length: between 3 and 63 characters.
    • It can only contain lowercase Latin letters, numbers, and hyphens.
    • It must start with a letter and cannot end with a hyphen.

    The --name parameter is optional. You can create a registry without a name and use its ID to access it. The name field is user-defined. It is used when listing resources in the Yandex Cloud CLI and is not used in the Docker CLI.

  3. Make sure the registry has been created:

    yc container registry list
    

    Result:

    +----------------------+--------+----------------------+
    |          ID          |  NAME  |      FOLDER ID       |
    +----------------------+--------+----------------------+
    | crpd50616s9a******** | my-reg | b1g88tflru0e******** |
    +----------------------+--------+----------------------+
    

If you do not have Terraform yet, install it and configure the Yandex Cloud provider.

To manage infrastructure using Terraform under a service account or user accounts (a Yandex account, a federated account, or a local user), authenticate using the appropriate method.

  1. Include the parameters of the registry you want to create in the configuration file, e.g., a file named example.tf in the ~/cloud-terraform directory:

    resource "yandex_container_registry" "my-reg" {
      name = "my-registry"
      folder_id = "<folder_ID>"
      labels = {
        my-label = "my-label-value"
      }
    }
    

    Where:

    • name: Registry name.
    • folder_id: Folder ID.
    • labels: Labels used.

    For more information about resources you can create with Terraform, see this provider guide.

  2. Make sure the configuration file is correct.

    1. In the terminal, navigate to the directory with your configuration file:

      cd /Users/<username>/cloud-terraform
      
    2. Run a check using this command:

      terraform plan
      

      Result:

      Refreshing Terraform state in-memory prior to plan...
      The refreshed state will be used to calculate this plan, but will not be
      persisted to local or remote state storage.
      ...
      Note: You did not specify an "-out" parameter to save this plan, so Terraform
      cannot guarantee that exactly these actions will be performed if
      "terraform apply" is subsequently run.
      
  3. Create a registry.

    1. Run this command:

      terraform apply
      

      Result:

      An execution plan has been generated and is shown below.
      Resource actions are indicated with the following symbols:
        + create
      ...
        Terraform will perform the actions described above.
        Only 'yes' will be accepted to approve.
      
        Enter a value:
      
    2. Confirm creating the registry by typing yes and pressing Enter:

      Enter a value: yes
      

      Result:

      yandex_container_registry.default: Creating...
      yandex_container_registry.default: Creation complete after 4s [id=crpuljdfqoj3********]
      
      Apply complete! Resources: 1 added, 0 changed, 0 destroyed.
      

      This will create a registry named my-registry in the folder.

    3. Check the resources and their settings in the management console.

To create a registry, use the create method for the Registry resource.

Was the article helpful?

Previous
Getting information about a registry access policy
Next
Configuring access to a registry
© 2026 Direct Cursus Technology L.L.C.