vania-janet/multiturn-rag-retrieval-data huggingface dataset:
In which case, you can use Container Registry in [local regions](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_overviewregistry_regions_local).

All registry artifacts are scoped to the specific registry instance (one of the regional registries or the global registry) that you are currently working with. For example, namespaces, images, quota settings, and plan settings must all be managed separately for your account in each registry instance.



 Global registry 

A global registry is available. The global registry doesn't include a region in its name (icr.io). In addition to hosting user namespaces and images, this registry also hosts public images that are provided by IBM.

The global instance of Container Registry is available by using the [domain names](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_overviewoverview_elements_domain_name) that are shown in the following table.



Table 3. Domain name for the global registry

 Registry Domain name Private domain name Deprecated domain name 

 Global icr.io private.icr.io registry.bluemix.net 



To learn about connecting to Container Registry by using the private domain names, see [Using private network connections](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_privateregistry_private_images).

The existing bluemix.net domain names are deprecated, but you can continue to use them for the moment. An end of support date is not available yet.



 Targeting the global registry 

You can target the global registry by running the [ibmcloud cr region-set](https://cloud.ibm.com/docs/Registry?topic=Registry-containerregclibx_cr_region_set) command.



1. To target the global registry, run the following command.

ibmcloud cr region-set global
2.
[IBM Cloud Container Registry](https://cloud.ibm.com/docs/Registry?topic=Registry-getting-started) IBM Cloud® Container Registry provides a multi-tenant, highly available, scalable, and encrypted private image registry that is hosted and managed by IBM®. [Platform metrics](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_monitor) 
 [IBM Cloud® Kubernetes Service](https://cloud.ibm.com/docs/containers?topic=containers-getting-started) You can use the IBM Cloud Kubernetes Service service to deploy highly available apps in Docker containers that run in Kubernetes clusters. [Metrics sent by agent](https://cloud.ibm.com/docs/containers?topic=containers-health-monitormonitoring) 
 [Red Hat® OpenShift® on IBM Cloud®](https://cloud.ibm.com/docs/openshift?topic=openshift-getting-started) With Red Hat OpenShift on IBM Cloud, you can deploy apps on highly available clusters that come installed with the Red Hat OpenShift on IBM Cloud Container Platform software installed on Red Hat Enterprise Linux. [Metrics sent by agent](https://cloud.ibm.com/docs/openshift?topic=openshift-health-monitoropenshift_monitoring) 







 Database services 

The following table lists database services that are enabled for IBM Cloud Monitoring:



Table 3. List of database services

 Service Description Metrics 

 [IBM Cloudant](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-getting-started-with-cloudant) IBM Cloudant is a document-oriented database as a service (DBaaS). It stores data as documents in JSON format. [Platform metrics](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-monitor-ibm-cloud-pm)
* [Cost of Container Registry](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_overviewregistry_cost)



* [Upgrading your service plan](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_overviewregistry_plan_upgrade)
* [Terms that are used in IBM Cloud Container Registry](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_overviewoverview_elements)



* [Container image](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_overviewoverview_elements_container_image)
* [Digest](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_overviewoverview_elements_digest)
* [Dockerfile](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_overviewoverview_elements_dockerfile)
* [Docker V2 container images](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_overviewoverview_elements_dockerv2_images)
* [Domain name](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_overviewoverview_elements_domain_name)
* [Image manifest](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_overviewoverview_elements_manifest)
* [OCI container images](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_overviewoverview_elements_oci_images)
* [Registry](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_overviewoverview_elements_registry)
* [Registry namespace](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_overviewoverview_elements_namespace)
* [Repository](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_overviewoverview_elements_repository)
As an alternative approach, Container Registry supports the [Red Hat Signing](https://www.redhat.com/en/blog/container-image-signing) model. For more information, see [Signing images for trusted content by using Red Hat signatures](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_trustedcontentregistry_trustedcontent_red_hat_sig).





 21 June 2021 

Global registry
: The global registry (icr.io) is now available for hosting user images and namespaces. Previously the global registry hosted only public images that are provided by IBM. For more information, see [Global registry](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_overviewregistry_regions_global).





 10 May 2021 

New region in Canada
: A new region in Toronto, Canada is available. The new region is ca-tor and the domain name is ca.icr.io. For more information, see [Local regions](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_overviewregistry_regions_local).





 4 May 2021 

The ibmcloud cr ppa-archive-load command is discontinued
: The ibmcloud cr ppa-archive-load command is discontinued. Containerized software is distributed in IBM Cloud Paks, see [IBM Cloud Paks](https://www.ibm.com/cloud-paks). To run IBM Cloud Paks on Red Hat OpenShift on IBM Cloud, see [Adding Cloud Paks](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_cloud_paks). For more information about setting up your IBM Cloud Kubernetes Service cluster to pull entitled software, see [Setting up a cluster to pull entitled software](https://cloud.ibm.com/docs/containers?topic=containers-registrysecret_entitled_software).





 18 February 2021
Why can't I connect to Container Registry? 

You are unable to connect to IBM Cloud® Container Registry and you get the message connection reset.

  What’s happening 

You can't connect to IBM Cloud Container Registry and you receive the following message: connection reset.

  Why it’s happening 

The following alternatives are possible causes:



*  Firewall or Calico rules are in place.
*  The connection to Container Registry is through a proxy.
*  IP allowlists are configured.
*  Context-based restrictions are configured.



  How to fix it 

You can fix this problem in the following ways:



*  Check your [firewall](https://cloud.ibm.com/docs/Registry?topic=Registry-troubleshoot-firewall&interface=ui) or [Calico](https://www.tigera.io/project-calico/) rules.
*  Connect to Container Registry without a proxy.
*  Use IP addresses that are in your allowlist.
*  Ensure that your [context-based restrictions](https://cloud.ibm.com/docs/Registry?topic=Registry-iam&interface=uiiam_cbr) give you access to Container Registry.
Container Registry supports the [Red Hat Signing](https://www.redhat.com/en/blog/container-image-signing) model. For more information, see [Signing images for trusted content by using Red Hat signatures](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_trustedcontentregistry_trustedcontent_red_hat_sig).





 5 October 2021 

Container Registry container builds are discontinued
: The ibmcloud cr build command is discontinued from 5 October 2021. You can use [Tekton pipelines](https://cloud.ibm.com/docs/ContinuousDelivery?topic=ContinuousDelivery-pipeline_container_imagespipeline_tekton_images) instead.

For more information, see [IBM Cloud Container Registry is Deprecating Container Builds](https://www.ibm.com/cloud/blog/announcements/ibm-cloud-container-registry-deprecating-container-builds).





 2 September 2021 

Namespaces that are assigned to a resource group show in the Resource list page
: Namespaces that are assigned to a resource group show in the Resource list page of the IBM Cloud console. For more information, see [Planning namespaces](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_setup_cli_namespaceregistry_setup_cli_namespace_plan).





 30 August 2021 

New region in Brazil
: A new region in Sao Paulo, Brazil is available. The new region is br-sao and the domain name is br.icr.io. For more information, see [Local regions](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_overviewregistry_regions_local).





 19 August 2021 

Using registry tokens is discontinued
: From 19 August 2021, registry tokens are no longer accepted for authentication.
IBM Cloud® Container Registry provides a multi-tenant private image registry that you can use to store and share your container images with users in your IBM Cloud account.

Kubernetes service Container Registry



* 45 minutes
* 2023-06-02



[Encrypting images for content confidentiality](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_encrypt)Encrypting images for content confidentiality

You can protect the confidentiality of your IBM Cloud® Container Registry images, and ensure that hosts that aren't trusted can't run the images.

Key Protect Container Registry



* 2 hours
* 2023-01-25



[Granting access to Container Registry resources tutorial](https://cloud.ibm.com/docs/Registry?topic=Registry-iam_access)Granting access to Container Registry resources tutorial

Use this tutorial to find out how to grant access to your resources by configuring IBM Cloud® Identity and Access Management (IAM) for IBM Cloud® Container Registry.

Container Registry



* 45 minutes
* 2023-01-31



[Container Registry and Vulnerability Advisor workflow tutorial](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_tutorial_workflow)Container Registry and Vulnerability Advisor workflow tutorial

Use this tutorial to find out about the basic functions of both IBM Cloud® Container Registry and Vulnerability Advisor.

Kubernetes service Container Registry



* 2 hours
* 2023-06-19



[Onboarding a Certified Operator from a Red Hat registry](https://cloud.ibm.com/docs/account?topic=account-catalog-opbundle-tutorial)Onboarding a Certified Operator from a Red Hat registry

This tutorial walks you through how to onboard a sample Operator bundle from a Red Hat® registry to your account. By completing this tutorial, you learn how to create a private catalog in your account, import the Operator bundle, and validate that it can be installed on a Red Hat OpenShift on IBM Cloud cluster.

Container Registry Managing your account, resources, and access



* 45 minutes
* 2022-10-26
Accessing container registries 

Images that are used by IBM Cloud® Code Engine are typically stored in a registry that can either be accessible by the public (public registry) or set up with limited access for a small group of users (private registry).

A container registry, or registry, is a service that stores container images. For example, IBM Cloud Container Registry and Docker Hub are container registries. A container registry can be public or private. A container registry that is public does not require credentials to access. In contrast, accessing a private registry does require credentials.

Code Engine requires access to container registries to complete the following actions:



* To retrieve (or "pull") a container image to run an app or job
* To store a newly created container image as an output of an image build
* To store and retrieve local files when a build is run from local source



Code Engine handles many of the underlying details of the interactions between the system and your registry.

To pull images from a registry, Code Engine uses a special type of Kubernetes secret that is called an imagePullSecret. This image pull secret stores the credentials to access a container registry. When you add access to a container registry with Code Engine to pull images, you are creating an image pull secret. For more information about image pull secrets, see [Kubernetes documentation](https://kubernetes.io/docs/home/).



 Types of image registries 

Images are typically stored in a registry that can either be accessible by the public (public registry) or set up with limited access for a small group of users (private registry).

Public registries, such as public Docker Hub, can be used to get started with Docker and Code Engine to create your first application or job. But when it comes to enterprise workloads, use a private registry, such as the one provided in IBM Cloud Container Registry to protect your images from being used by unauthorized users. For private registries, use registry secrets to ensure that the credentials are available to gain access to the private registry.



Table 1. Public and private image registry types

 Registry Description
IBM Cloud Container Registry CLI 

You can use the IBM Cloud® Container Registry CLI, which is provided in the container-registry CLI plug-in, to manage your

registryand its resources for your IBM Cloud account.



 Prerequisites 

Before you can use the Container Registry CLI, you must complete the following prerequisites.



1. Install the ibmcloud CLI plug-in, see [Getting started with the IBM Cloud CLI](https://cloud.ibm.com/docs/cli?topic=cli-getting-started).
2. Install the container-registry CLI plug-in, see [Installing the container-registry CLI plug-in](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_setup_cli_namespace&interface=uicli_namespace_registry_cli_install).
3. Log in to IBM Cloud with the ibmcloud login command to generate anaccess tokenand authenticate your session so that you can run commands in the CLI.





 Notes 

To find out how to use the Container Registry CLI, see [Getting started with IBM Cloud Container Registry](https://cloud.ibm.com/docs/Registry?topic=Registry-getting-startedgetting-started).

You're notified on the command line when updates to the ibmcloud CLI and container-registry CLI plug-ins are available. Ensure that you keep your CLIs up to date so that you can use all the available commands and options. If you want to view the current version of your container-registry CLI plug-in, run the ibmcloud plugin list command.

For more information about the IAM platform and service access roles that are required for some Container Registry commands, see [Managing IAM access for Container Registry](https://cloud.ibm.com/docs/Registry?topic=Registry-iam).

Do not put personal information in your container images, namespace names, description fields, or in any image configuration data (for example, image names or image labels).
* [Setting up a cluster to pull entitled software](https://cloud.ibm.com/docs/containers?topic=containers-registrysecret_entitled_software)
* [Updating an IBM Cloud Kubernetes Service containerd custom registry configuration](https://cloud.ibm.com/docs/containers?topic=containers-registryupdate_containerd_registry_config)



* [Example daemonset to update a containerd custom registry configuration](https://cloud.ibm.com/docs/containers?topic=containers-registryds-example-registry)





[Setting up continuous integration and delivery](https://cloud.ibm.com/docs/containers?topic=containers-cicdcicd)



* [Supported automation tools](https://cloud.ibm.com/docs/containers?topic=containers-cicdcicd_strategy)
* [Setting up a continuous delivery pipeline for a cluster](https://cloud.ibm.com/docs/containers?topic=containers-cicdcontinuous-delivery-pipeline)







 Developing and deploying apps 

[Planning app deployments](https://cloud.ibm.com/docs/containers?topic=containers-plan_deployplan_deploy)



* [Moving workloads to IBM Cloud Kubernetes Service](https://cloud.ibm.com/docs/containers?topic=containers-plan_deploymoving)



* [What kind of apps can I run in IBM Cloud Kubernetes Service?](https://cloud.ibm.com/docs/containers?topic=containers-plan_deployapp_types)
* [What are some guidelines for developing stateless, cloud-native apps?](https://cloud.ibm.com/docs/containers?topic=containers-plan_deploy12factor)
* [What about serverless apps?](https://cloud.ibm.com/docs/containers?topic=containers-plan_deployapps_serverless)
* [I already have an app. How can I migrate it to IBM Cloud Kubernetes Service?]
Setting up an image registry 

Plan and set up an image registry so that developers can create app containers in IBM Cloud® Kubernetes Service by using Docker images.



 Planning image registries 

Images are typically stored in a registry that can either be accessible by the public (public registry) or set up with limited access for a small group of users (private registry).

Public registries, such as Docker Hub, can be used to get started with Docker and Kubernetes to create your first containerized app in a cluster. But when it comes to enterprise applications, use a private registry, like the one provided in IBM Cloud Container Registry to protect your images from being used and changed by unauthorized users. Private registries must be set up by the cluster admin to ensure that the credentials to access the private registry are available to the cluster users.

You can use multiple registries with IBM Cloud Kubernetes Service to deploy apps to your cluster.



Public and private image registry options

 Registry Description Benefit 

 [IBM Cloud Container Registry](https://cloud.ibm.com/docs/Registry?topic=Registry-getting-startedgetting-started) With this option, you can set up your own secured Docker image repository in IBM Cloud Container Registry where you can safely store and share images between cluster users. <br><br> * Manage access to images in your account.<br> * Use IBM provided images and sample apps, such as IBM Liberty, as a parent image and add your own app code to it.<br> * Automatic scanning of images for potential vulnerabilities by Vulnerability Advisor, including OS specific recommendations to fix them.<br><br><br> 
 Any other private registry Connect any existing private registry to your cluster by creating an [image pull secret](https://kubernetes.io/docs/concepts/containers/images/). The secret is used to securely save your registry URL and credentials in a Kubernetes secret. Use existing private registries independent of their source (Docker Hub, organization owned registries, or other private Cloud registries).
The global registry domain name doesn't include a region (icr.io). Only public images that are provided by IBM are hosted in this registry.

For more information, see [Global registry](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_overviewregistry_regions_global).





 29 September 2017 

Build Docker images
: The ibmcloud cr build command is now available for running container builds. You can build a Docker image directly in IBM Cloud or create your own Docker image on your local computer and upload (push) it to your namespace in Container Registry.

For more information, see [Building Docker images to use them with your namespace](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_images_registry_images_creating).





 24 August 2017 

Graphical user interface released
: The IBM Cloud Container Registry graphical user interface is available in the catalog, see [Container Registry](https://cloud.ibm.com/registry/catalog).





 27 June 2017 

Introducing IBM Cloud Container Registry
: IBM Cloud Container Registry is available as a service in IBM Cloud. [Container Registry](https://www.ibm.com/cloud/container-registry) provides a multi-tenant private image registry that you can use to store and share your container images with users in your IBM Cloud account.

For more information about how to use Container Registry, see [Getting started with Container Registry](https://cloud.ibm.com/docs/Registry?topic=Registry-getting-started).
Getting started with Container Registry 

IBM Cloud® Container Registry provides a multi-tenant private image [registry](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_overviewoverview_elements_registry) that you can use to store and share your [container images](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_overviewoverview_elements_container_image) with users in your IBM Cloud account.

The IBM Cloud console includes a brief Quick Start. To find out more about how to use the IBM Cloud console, see [Managing image security with Vulnerability Advisor](https://cloud.ibm.com/docs/Registry?topic=Registry-va_index&interface=ui).

Do not put personal information in your container images, namespace names, description fields, or in any image configuration data (for example, image names or image labels).



 Before you begin 

Install the IBM Cloud CLI so that you can run the IBM Cloud ibmcloud commands, see [Getting started with the IBM Cloud CLI](https://cloud.ibm.com/docs/cli?topic=cli-getting-started).





 Step 1: Install the Container Registry CLI 



1. Install the container-registry CLI plug-in by running the following command:

ibmcloud plugin install container-registry

For more information about installing plug-ins, see [Extending IBM Cloud CLI with plug-ins](https://cloud.ibm.com/docs/cli?topic=cli-plug-ins).







 Step 2: Set up a namespace 

Create a [namespace](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_overviewoverview_elements_namespace). The namespace is created in the [resource group](https://cloud.ibm.com/docs/account?topic=account-rgs) that you specify so that you can configure access to resources within the namespace at the resource group level. If you don't specify a resource group, and you don't target a resource group, the default resource group is used.
: Container Registry now supports Red Hat signatures.

For more information, see [Signing images for trusted content by using Red Hat® signatures](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_trustedcontentregistry_trustedcontent_red_hat_sig).





 25 October 2019 

IBM Log Analysis platform services logs are available
: Container Registry generates platform services logs that are displayed in your logging instances.

For more information, see [IBM Log Analysis platform services logs](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_logs).





 14 October 2019 

ibmcloud cr manifest-inspect command is available
: The ibmcloud cr manifest-inspect command displays the contents of the manifest for an image.

For more information, see [ibmcloud cr manifest-inspect](https://cloud.ibm.com/docs/Registry?topic=Registry-containerregclibx_cr_manifest_inspect).





 23 September 2019 

You can create retention policies for your images
: Image retention policies retain the specified number of images for each repository within a namespace in Container Registry. All other images in the namespace are deleted.

The following commands are available for you to use to create retention policies so that you can manage your images:



* The [ibmcloud cr retention-policy-set](https://cloud.ibm.com/docs/Registry?topic=Registry-containerregclibx_cr_retention_policy_set) command sets up a policy for retaining images for each repository within a namespace.
* The [ibmcloud cr retention-policy-list](https://cloud.ibm.com/docs/Registry?topic=Registry-containerregclibx_cr_retention_policy_list) command lists the image retention policies for your account.



For more information, see [Retaining images](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_retention).

You can restore deleted images from the trash
: All deleted images are stored in the trash for 30 days.

The following commands are available for you to use to restore images: