Available in Classic and VPC
View supported environments, integrated services, service limits, pricing plans, etc., for smooth use of Container Registry.
Cloud environment specifications
Container Registry supports the following cloud environment specifications:
| Item | Specifications |
|---|---|
| Region (zone) | Korea and Singapore |
| Classic | Support |
| VPC | Support |
| Region code | |
| Language | Korean, English, and Japanese |
For more information on the VPC environment, see Service introduction on the NAVER Cloud Platform portal, and for more information on whether the VPC environments are supported for each service, see Ncloud user environment guide.
- 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
- Public endpoint:
- 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 may be needed, leading to possible extra charges.
- When accessing through the private endpoint, which corresponds to a private communication section, network charges may apply when communicating with Object Storage buckets.
Required related services
The private Docker container images in the Container Registry are stored by connecting to Object Storage. Therefore, 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 Object Storage user guide.
Service limits
Docker Version
To use NAVER Cloud Platform’s Container Registry, you need Docker Engine 1.13 or higher.
Object Storage
- To use Container Registry, subscribe to NAVER Cloud Platform’s Object Storage. The Docker container images are stored in the bucket of Object Storage.
- Enabling the following features may disrupt normal service usage:
- 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 set.
Pricing information
Private Docker container images are stored by integrating with Object Storage. Therefore, the amount of stored data, the number of API requests, and network transmission fees are separately charged based on usage. For details of Container Registry's usage fee, see the pricing information at Portal > Services > Containers > Container Registry.