---
title: "Container Registry prerequisites"
slug: "containerregistry-spec"
tags: ["Container Registry"]
updated: 2026-09-17T09:31:39Z
published: 2026-09-17T09:31:39Z
canonical: "guide.ncloud-docs.com/containerregistry-spec"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://guide.ncloud-docs.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Container Registry prerequisites

Available in Classic and VPC

View supported environments, integrated services, service limits, pricing plans, etc., to ensure smooth use of Container Registry.

## Cloud specifications

Container Registry supports the following cloud specifications:

| Item | Specifications |
| --- | --- |
| Region (zone) | Korea, Singapore and Japan |
| Classic | Supported |
| VPC | Supported |
| Region code | - Korea (KR): kr - Singapore (SGN): sg - Japan (JPN): jp |
| Language | Korean, English, and Japanese |

              Note

              

For more information about the VPC environment, see [VPC overview](https://www.ncloud.com/product/networking/vpc) on the NAVER Cloud Platform portal. To verify VPC support for specific services, see [Ncloud user environment guide](/docs/en/environment-environment-1-1).

              Note

              

- The Region code serves as the endpoint of the registry. The registry name and Region code are used as the registry endpoints, as follows: You can deactivate the public endpoint if needed, making it unusable.
  - Public endpoint: `<registry-name>`.`<region-code>`.ncr.ntruss.com
  - Private endpoint: `<random-id>`.`<region-code>`.private-ncr.ntruss.com
- When accessing through the public endpoint, it is necessary to set up an environment for external internet usage. If configured with a NAT Gateway and a Public Subnet, additional resources such as a Public IP are needed, leading to possible extra charges.
- When accessing via a private endpoint, network charges may apply for communication with the integrated storage buckets as it is considered private network traffic.

## Required related services

Private Docker container images in Container Registry are stored through integration with storage services. When creating a registry, you can choose the storage type to integrate with (Object Storage or Ncloud Storage). The prerequisites vary depending on the selected storage type.

- Object Storage: You need to subscribe to Object Storage before subscribing to the Container Registry service, and create a bucket to store private Docker container images. For more information, see the [Object Storage user guide](/docs/en/storage-storage-6-1).
- Ncloud Storage: If you select Ncloud Storage when creating a registry, a bucket for storing images is automatically created and integrated. For more information, see the [Ncloud Storage user guide](/docs/en/ncloudstorage-overview).

              Note

              

Ncloud Storage is available in the Korea Region only.

## Service limits

Service limits for using Container Registry are as follows:

### Docker version

To use NAVER Cloud Platform’s Container Registry, you need Docker Engine 1.13 or higher.

### Object Storage

- If you choose Object Storage as the storage type for integration, you must subscribe to the Object Storage service from the NAVER Cloud Platform. Docker container images are stored in an Object Storage bucket.
- Enabling the following features may prevent the service from operating normally.
  - WORM(Write Once Read Many)
  - Lifecycle Management
  - ACL(Access Control List)
- If the ACL feature is activated, you can use the Container Registry service by accessing a private endpoint within the server with access control configured.

### Ncloud Storage

- If you select Ncloud Storage as the storage type for integration, enabling the Lifecycle Management feature may prevent the service from operating normally. If Docker container image objects are deleted due to lifecycle rules or transitioned to another storage class, such as Deep Archive Class, the images cannot be downloaded (pulled) properly.

## Pricing information

Private Docker container images are stored in the integrated storage. Therefore, charges for stored data volume, API requests, and network traffic are billed separately based on actual usage. For details about Container Registry's usage fee, see the pricing information at **Portal > Services > Containers > Container Registry**.

- [**Portal > Services > Containers > Container Registry**](https://www.ncloud.com/product/containers/containerRegistry)