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 overview

Prev Next

Available in Classic and VPC

NAVER Cloud Platform's Container Registry is a private Docker container image repository based on the Docker Registry v2 specification that allows you to easily store, manage and deploy container images. Developers can simplify container development by reducing the need to build their own container registry and worry about infrastructure.

Container Registry features

Container Registry offers these key features:

  • Manage Docker container images: You can use integrated server of Container Registry with NAVER Cloud Platform, define registries (image repositories) in Container Registry using namespaces, and manage Docker container image viewing, deletion and metadata through Container Registry's dashboard.
  • Docker support and integration with Container Registry: Supports Docker Registry HTTP API V2 and integrates with NAVER Cloud Platform’s Container Registry using Docker CLI commands.
  • Collaboration and access control with permission segmentation: You can set API task actions (Change, View) that users can perform on the Docker Container Registry, allowing them to share repositories with other users. You can also use Sub Accounts to control and monitor permissions, and assign different permissions for different users and roles, allowing for fine-grained access control.
    • Manager (change, view) permissions: Permissions to upload (Push)/download (Pull) Docker container images to the Container Registry and delete registries and container images.
    • View permissions: Container image download (Pull) permissions.
  • Provide public/private endpoints: Provides public endpoints and private endpoints that can be safely used only within the internal network environment of the NAVER CLOUD Platform, and private endpoints enhance security by preventing user access from external networks.
  • Enhance security with container vulnerability analysis: Analyze security vulnerabilities of container images registered in the Container Registry to identify them based on CVE schemes and mitigate vulnerabilities using the scan results provided to enhance container security.
  • Storing container images in the cloud: Save uploaded private Docker container images in NAVER Cloud Platform’s storage, allowing developers to focus on container development without worrying about infrastructure for image storage.

Container Registry user guide

Container Registry is available in the Korea and Singapore Regions. Use this guide to get the most out of Container Registry.

Container Registry related resources

Beyond the user guide, these resources provide additional context and support for Container Registry. Whether you're considering Container Registry or need in-depth information for development, marketing, and other purposes, these resources can help:

FAQs

Before you read the user guides, you can quickly resolve your queries by checking answers our FAQs. If you haven't found the answer to your question in the FAQs below, search the user guide for the information you need.

Q. How do I log in to Container Registry from a CLI environment?

  • If you select the registry that you want to log in to from the Container Registry menu in NAVER Cloud Platform console, you can see the login command in the Access Commands section on the details page.
  • Use the authentication key for the ID and password to log in to the registry. To generate an authentication key, see Ncloud API. Use your Access Key ID as your username and your Secret Key as your password.
  • When logging in to the registry with a sub account, the username is the sub account's API authentication key. If API Gateway Access is enabled for the sub account's Access Type, you can view and manage the details of the API authentication key by navigating to Menu > **Services **> Management & Governance > Sub Account in the NAVER Cloud Platform console, selecting the sub account, and opening the [Access Key] tab.

Q. Can I grant permissions to sub-accounts for Container Registry?

  • You can grant permissions to the registry from the Menu > Services > Management & Governance > Sub Account > Sub Accounts menu in the NAVER Cloud Platform console.
  • There are manager (NCP_CONTAINER_REGISTRY_MANAGER) and viewer (NCP_CONTAINER_REGISTRY_VIEWER) permissions. The manager has push and pull permissions for Docker container images, and the viewer has pull permissions only.
  • In addition, the manager is granted permissions to create and delete registries, delete images, and edit metadata.

Q. Can I enter notes for images uploaded to Container Registry?

  • You can enter notes on uploaded images in two forms, short Description and Full Description via Container Registry.
  • For Short description, simple notes under 100 characters can be entered.
  • The Full description supports Markdown format, which allows a richer description of metadata for the image.

Q. What is the pricing for Container Registry?

  • There is no separate management fee for Container Registry, and you are billed for the usage of storage associated with the registry. Charges apply based on the amount of data stored in the integrated storage, the number of API requests, and the volume of network traffic.

Q. Can I edit the contents of buckets in the storage that are integrated with the Container Registry?

  • Container Registry integrates with the storage to provide push and pull features for private Docker container images. Be cautious when editing or deleting the contents of the integrated storage bucket, this may compromise normal operations.

Q. What are private endpoints? (VPC)

  • A private endpoint is a Container Registry endpoint that can only be used within NAVER Cloud Platform's VPC network. This ensures that all network traffic is restricted to NAVER Cloud Platform’s network for enhanced security.
  • 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.

Q. What are private endpoints? (Classic)

  • A private endpoint is a Container Registry endpoint that can only be used within NAVER Cloud Platform's Classic network. This ensures that all network traffic is restricted to NAVER Cloud Platform’s network for enhanced security.