text: An instance name cannot be used to create an instance for the following reasons:
  To log in to the instance, you should run the command
  docker login in the access client and enter the user name and password.
  Follow the instructions below:
  If the problem persists, please submit a ticket to contact us.
  We recommend the TKE user to use the TCR add-on to implement the secret-free pulling of images. For more information, see TKE Clusters Use the TCR Addon to Enable Secret-free Pulling of Container Images via Private Network.
  You can set the access level of the namespace where the image is located to public, and all image repositories and Helm Charts in this namespace will become public. As "Anonymous Access" is enabled for instance by default, any clients that pass access control can get the images and charts directly without logging in. We recommend that you only set the basic image repository.
  When the Docker client is used to push and pull images, the client must have the credential for accessing registry instances. To solve the problem, refer to the following steps:
  docker logincommand on the server and the access credential of the instance has been stored in the Docker client. For more information, refer to Pushing and Pulling an Image.
  Yes. When you delete a specified image version, the image versions with the same content (namely the same SHA256) will also be deleted.
  In TCR, you can configure the resource access permission for the sub-account through CAM. For more information, see Example of Authorization Solution of the Enterprise Edition or Example of Authorization Solution of the Personal Edition.
  Using the public network to upload and download the cloud-native applications such as container images and Helm charts will generate public network traffic fees in COS. We recommend you to use the private network access because it will not incur traffic fees, and the access speed is better than public network access.
  Note
  Using the instance synchronization feature for cross-regional synchronization of container images and Helm charts will not generate COS public network traffic fees.
  By default, the private network is used for VPC and the public network is used for non-VPC. For more information, see How do I determine if I am accessing COS over a private network?.
  It may be that the password was entered incorrectly five times, or the admin locks it. Please contact your admin.
  Currently, TCR supports the accelerated pull of images outside the Chinese mainland and P2P image acceleration.
  Based on COS cross-region synchronization capability, the instance replication supports real-time streaming synchronization of image data and is faster than instance synchronization.
  The instance replication feature is only available for the premium instance and the cross-border replication is not supported.
  The image is compressed and stored in the image repository. The image size on the cluster node shall prevail.
  Currently, the CODING DevOps related features and some new features are not supported in the international version.
  Contact our sales team or business advisors to help your business.
  Open a ticket if you're looking for further assistance. Our Ticket is 7x24 avaliable.
  Was this page helpful?