vania-janet/multiturn-rag-retrieval-data huggingface dataset:
For example, you can use the following script, where <old_namespace> is the existing namespace and <new_namespace> is the namespace that you created:

IMAGES=$(icr images --restrict <old_namespace> --format "{{ .Repository }}:{{ .Tag }}")

for i in $IMAGES ; do
new=$(echo $i | sed "s|/<old_namespace>/|/<new_namespace>/|1")
ibmcloud cr image-tag $i $new
done





 Do images in the trash count toward my quota? 

Images that are in the trash don't count toward your quota.





 How do I find the image digest? 

You can find the long format of the image [digest](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_overviewoverview_elements_digest) by running one of the following commands. The digest is displayed in the Digest column of the CLI.

When you are using the digest to identify an image, always use the long format.



* Run the [ibmcloud cr image-digests](https://cloud.ibm.com/docs/Registry?topic=Registry-containerregclibx_cr_image_digests) command:

ibmcloud cr image-digests
* Run the [ibmcloud cr image-list](https://cloud.ibm.com/docs/Registry?topic=Registry-containerregclibx_cr_image_list) command:

ibmcloud cr image-list --no-trunc

If you run the ibmcloud cr image-list command without the --no-trunc option, you see the truncated format of the digest.







 How do I use digests to work with images?
Images remain in the trash for 30 days after they are deleted from your live repository.

If you want to restore an image from the trash, run the [ibmcloud cr image-restore](https://cloud.ibm.com/docs/Registry?topic=Registry-containerregclibx_cr_image_restore) command, see [Restoring images](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_images_registry_images_restore).

ibmcloud cr trash-list [--restrict NAMESPACE] [--json]



 Prerequisites 

To find out about the required permissions, see [Access roles for using Container Registry](https://cloud.ibm.com/docs/Registry?topic=Registry-iamaccess_roles_using).





 Command options 

--restrict NAMESPACE
: (Optional) Limit the output to display only images in the specified namespace.

--json
: (Optional) Outputs JSON that contains the details of the contents of the trash.





 Example 

Display the images that are in the trash in the birds namespace.

ibmcloud cr trash-list --restrict birds







 ibmcloud cr va-version 

Find out which version of Vulnerability Advisor you're using.

Vulnerability Advisor version 3 is deprecated from 19 June 2023. For more information about how to update to version 4, see [Update Vulnerability Advisor to version 4 by 19 June 2023](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_notices_va_v4&interface=ui).

ibmcloud cr va-version



 Prerequisites 

None.







 ibmcloud cr va-version-set 

Set the version of Vulnerability Advisor. You can set the version to either v3, the default, or v4. If you want to use version 4 temporarily, see [Setting the Vulnerability Advisor version](https://cloud.ibm.com/docs/Registry?topic=Registry-va_index&interface=uiva_set_version).

Vulnerability Advisor version 3 is deprecated from 19 June 2023.
Why can't I pull the newest image by using the latest tag? 

You're unable to pull the most recent image by using the latest

tagin IBM Cloud® Container Registry.

  What’s happening 

You're trying to run the command docker pull, but it returned a version of your image that isn't the most recent version built.

  Why it’s happening 

The latest tag is applied by default to reference an image when you run Docker commands without specifying the tag value. The latest tag is applied to the most recent docker build or docker tag command that was run without a tag value explicitly set. Therefore, it's possible to run docker commands out of order or to explicitly set tags on some images. Both scenarios cause the latest tag to refer to a build that isn't the most recent.

  How to fix it 

It is generally better to explicitly define a different sequential tag for your images every time, and not rely on the latest tag.
Source Select the source for the custom image by choosing either [Virtual server instance boot volume](https://cloud.ibm.com/docs/vpc?topic=vpc-create-ifvimport-custom-image-vsi) (default) or [Block storage boot volume](https://cloud.ibm.com/docs/vpc?topic=vpc-create-ifvimport-custom-image-vol). 
 Manage image lifecycle (optional) Select to schedule status changes for the image. You can schedule a single status change or schedule the complete lifecycle of the images. The image statuses are:<br><br><br><br> * available: The image can be used to create an instance.<br> * deprecated: The image is still available to use to provision and instance. Using the deprecated status can discourage use of the image before the status changes to obsolete.<br> * obsolete: The image is not available to use to provision an instancce.<br> * Schedule complete lifecycle: You can schedule both the deprecated and obsolete status changes at the same time.<br><br><br><br>You can move back and forth between the three statuses. Only the statuses you can change to are displayed. You can schedule status changes by using calendar date and time or number of days. The obsolescence date must always be after the deprecation date. 







 Create an image from a virtual server instance boot volume 

When you select Virtual server instance boot volume as the source of your custom image, a list of instances displays. To create an image from the instance's boot volume:



1. On the Import custom image page, select Virtual server instance boot volume (default).

To create an image of the boot volume associated with an instance, the virtual server instance must be stopped.
2. Optionally, stop a running instance by clicking the overflow menu (ellipsis) and click Stop.
3. Select an instance from the list. You're selecting the boot volume of the instance.
4.
In general, it is not recommended to configure the image to use for individual pipeline jobs. This method increases the effort to upgrade to a new image version since you must update each pipeline job. However, there might be circumstances in which you are required to configure the image for a specific pipeline job.



1. On the stage, click the Stage Configuration icon, and then click Configure Stage.
2. In the JOBS tab, click the job that you want to modify.
3. The Pipeline image version option shows the current image version that is available, and the version that you are using for the selected pipeline job. To change the image version to use the current version to run the pipeline job, select Latest.



To run pipeline jobs with the image that you selected on the pipeline configuration page, select Pipeline default.
Configuring Image Setting and Deleting Image 



1. Choose Manage Images and Manage Image Profiles, you will see the list of image belong to you (you are the image owner/admin).



![edit](https://cloud.ibm.com/docs-content/v1/content/b6c5dbb443b797203b2824b05472cac5ae8635da/cloud-for-education/images/editImage.png)



1. Click Edit button, you can edit the configuration of the image. It defines the number of CPU cores, size of the memory. We recommend to use 2000 as CPU speed.



* The name will be displayed on the drop-down menu when users select Image. Please use names that are easy to understand for users, such as software name and version, class name and code etc.
* The owner is the main manager of this image. You can transfer the owner to someone by replacing the name here. You have to know their email, for example, for user [xxx@domain.edu.ec](mailto:xxx@domain.edu.ec), add xxx@domain here.
* Description and Usage Notes will be displayed on the web page when users use it. You can add instructions on how to use the images.
* Maximum Concurrent usage can limit the number of concurrent users can use this image. It is usually used for the images which has restriction on software license.
* Available for checkout should be selected if the image is ready for students. Otherwise, students cannot see this image.
* Revision indicates the different versions this image has. You can have comments for each version, and select one version as production version, and delete any unwanted version. Production version will be automatically chosen when students reserve this image. You can delete any revisions

!
You can make an immediate status change by using the ibmcloud is image-deprecate or ibmcloud is image-obsolete commands. You can also schedule these status changes for a future date and time by using the ibmcloud is image-update command. Specify the name or ID of the custom image with the IMAGE variable.

To make an immediate status change, use one of the following examples.

You can make an immediate status change only if a future status change is not scheduled. To remove a scheduled status change, see [Remove a scheduled custom image lifecycle status change by using the CLI](https://cloud.ibm.com/docs/vpc?topic=vpc-managing-custom-images&interface=uischedule-reset-ilm-status-change-cli). After you remove the scheduled status change, you can make an immediate status change.



* Change the image lifecycle status to deprecate.

ibmcloud is image-deprecate IMAGE
* Change the image lifecycle status to obsolete.

ibmcloud is image-obsolete IMAGE



To schedule a status change, use the following example.

For the deprecate-at or obsolete-at option, specify a date in the ISO 8601 (YYYY-MM-DDThh:mm:ss+hh:mm) date and time format.



* YYYY is the four digit year
* MM is the two digit month
* DD is the two digit day
* T separates the date and time information
* hh is the two digit hours
* mm is the two digit minutes
* +hh:mm or -hh:mm is the UTC time zone



Thus, the date of 30 September 2023 at 8:00 p.m. in the North American Central Standard Time Zone (CST) would be 2023-09-30T20:00:00-06:00

When scheduling the date and time, you can't use your current date and time. For example, if it is 8 a.m. on June 12, then the scheduled date and time must be after 8 a.m. on June 12.
When you import a custom image by using the application programming interface (API), you can also schedule the lifecycle status changes of an IBM Cloud VPC custom image at the same time by using the [Create an image](https://cloud.ibm.com/apidocs/vpc/latestcreate-image) command.

The name can't be used by another image in the region and names that start with ibm- are reserved for system-provided images. Specify the file.href subproperty with the location of the image. Specify the operating_system.name subproperty with the name of the image operating system.

To schedule the deprecation_at or obsolescence_at properties, specify a date in the ISO 8601 (YYYY-MM-DDThh:mm:ss+hh:mm) date and time format.



* YYYY is the four digit year
* MM is the two digit month
* DD is the two digit day
* T separates the date and time information
* hh is the two digit hours
* mm is the two digit minutes
* +hh:mm or -hh:mm is the UTC time zone



Thus, the date of 30 September 2023 at 8:00 p.m. in the North American Central Standard Time Zone (CST) would be 2023-09-30T20:00:00-06:00

When scheduling the date and time, you can't use your current date and time. For example, if it is 8 a.m. on June 12, then the scheduled date and time must be after 8 a.m. on June 12. If you define both the deprecation_at and obsolescence_at dates and times, the obsolescence_at date must be after the deprecation_at date and time.

The following example imports a custom image with the name of my-image, source location of cos://us-south/my-bucket/my-image.qcow2, and the operating system for the image is debian-9-amd64. The image is scheduled to be deprecated on 2023-03-01T06:11:28+05:30.
On the Custom images tab, click the Actions icon ![More Actions icon](https://cloud.ibm.com/docs-content/v1/content/f02b9c9adcbb7328d95a45e105cec371d50f15eb/icons/action-menu-icon.svg) for a specific image and select from the available options.
3. Select Schedule lifecycle.
4. In Image status, select the status change for the image.
5. In Deprecation details, select whether to change status Immediately or to Schedule future date.
6. If you selected Schedule future date, you need to fill out the following:



* Select either By calendar date or By number of days.



* If you selected By calendar date, enter the date and time information. This is the date and time when the status change will occur.
* If you selected By number of days, put in the number of days that will pass before the status is changed.





7. Click Save.



Follow these steps to schedule the entire lifecycle of the image:

You can schedule the complete lifecycle for the image. The image is first deprecated and then changes to obsolete according to the schedule that you define. Use the following steps to schedule a lifecycle change.



1. In [IBM Cloud console](https://cloud.ibm.com/login), go to Menu icon ![Menu icon](https://cloud.ibm.com/docs-content/v1/content/f02b9c9adcbb7328d95a45e105cec371d50f15eb/icons/icon_hamburger.svg) > VPC Infrastructure > Compute > Images.
2. On the Custom images tab, click the Actions icon !
Delete the image us.icr.io/birds/bluebird:1.

ibmcloud cr image-rm us.icr.io/birds/bluebird:1







 ibmcloud cr image-tag 

Add a [tag](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_overviewoverview_elements_tag) that you specify in the command to an existing image, copy the tag to another repository, or copy the tag to a repository in a different namespace. When you copy a tag, any Red Hat® signatures for its [digest](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_overviewoverview_elements_digest) are also copied. The target image, TARGET_IMAGE, is the new image and the source image, SOURCE_IMAGE, is the existing image in IBM Cloud Container Registry. The source and target images must be in the same region. You can reference the source image that you want to tag by either digest, repository@digest, or by tag, repository:tag. You must reference the target image by tag.

You can identify source images by using either the digest <dns>/<namespace>/<repo>@<digest> or by tag <dns>/<namespace>/<repo>:<tag>. You must reference the target image by tag, <dns>/<namespace>/<repo>:<tag>. Where <dns> is the domain name, <namespace> is the namespace, <repo> is the repository, <digest> is the digest, and <tag> is the tag.

To find the names of your images, use one of the following alternatives:



* To identify your image by digest, run the ibmcloud cr image-digests command. Combine the content of the Repository column (repository) and the Digest column (digest) separated by an at (@) symbol to create the image name in the format repository@digest.
* To identify your image by tag, run the ibmcloud cr image-list command.
Select Schedule lifecycle.
4. In Image status, select the status change for the image.
5. In Deprecation details, select whether to change status Immediately or to Schedule future date.
6. If you selected Schedule future date, you need to fill out the following:



* Select either By calendar date or By number of days.



* If you selected By calendar date, enter the date and time information. This is the date and time when the status change will occur.
* If you selected By number of days, put in the number of days that will pass before the status is changed.





7. Click Save.



Use the following steps to schedule the entire lifecycle of the image:

You can schedule the complete lifecycle for the image. The image is first deprecated and then changes to obsolete according to the schedule that you define. Use the following steps to schedule a lifecycle change.



1. In [IBM Cloud console](https://cloud.ibm.com/login), go to Menu icon ![Menu icon](https://cloud.ibm.com/docs-content/v1/content/f02b9c9adcbb7328d95a45e105cec371d50f15eb/icons/icon_hamburger.svg) > VPC Infrastructure > Compute > Images.
2. On the Custom images tab, click the Actions icon ![More Actions icon](https://cloud.ibm.com/docs-content/v1/content/f02b9c9adcbb7328d95a45e105cec371d50f15eb/icons/action-menu-icon.svg) for a specific image and select from the available options.
3. Select Schedule lifecycle.
4. Select Schedule complete lifecycle.



* If you selected By calendar date, enter the date and time for when you want the status change occur.
* If you selected By number of days, put in the number of days that you want to pass before the status is changed.
For the deprecation_at or obsolescence_at properties, specify a date in the ISO 8601 (YYYY-MM-DDThh:mm:ss+hh:mm) date and time format.



* YYYY is the four digit year
* MM is the two digit month
* DD is the two digit day
* T separates the date and time information
* hh is the two digit hours
* mm is the two digit minutes
* +hh:mm or -hh:mm is the UTC time zone



Thus, the date of 30 September 2023 at 8:00 p.m. in the North American Central Standard Time Zone (CST) would be 2023-09-30T20:00:00-06:00

When scheduling the date and time, you can't use your current date and time. For example, if it is 8 a.m. on June 12, then the scheduled date and time must be after 8 a.m. on June 12. If you define both the deprecation_at and obsolescence_at dates and times, the obsolescence_at date must be after the deprecation_at date and time.



* Schedule a status change to deprecated.

curl -X PATCH "$vpc_api_endpoint/v1/images/$image_id?version=2022-11-21&generation=2" -H "Authorization: Bearer $iam_token" -d '{
"deprecation_at": "2023-03-01T06:11:28+05:30" }'
* Schedule a status change to obsolete.

curl -X PATCH "$vpc_api_endpoint/v1/images/$image_id?version=2022-11-21&generation=2" -H "Authorization: Bearer $iam_token" -d '{
“obsolescence_at": "2023-12-31T06:11:28+05:30" }'

If you want to change the deprecation_at and obsolescence_at date and time entries, you can run these commands again.
In [IBM Cloud console](https://cloud.ibm.com/login), go to Menu icon ![Menu icon](https://cloud.ibm.com/docs-content/v1/content/f02b9c9adcbb7328d95a45e105cec371d50f15eb/icons/icon_hamburger.svg) > VPC Infrastructure > Compute > Images.
2. On the Custom images tab, click the name of a custom image to view details about that image.
3. On the Image details page you can edit the name of the image, add tags, and copy the CRN for the image.
4. From the Actions menu of the Image details page, you can create a virtual server instance from the custom image or deleting the image. For a full list of possible actions, see [Managing custom images by using the UI](https://cloud.ibm.com/docs/vpc?topic=vpc-managing-custom-imagescustom-images-managing-ui).







 Viewing custom image details by using the CLI 

You can view the details of a custom image, such as name and ID, operating system and version, encryption status, deprecation or obsolescence dates, and assigned resource group, by using the command-line interface (CLI).

To view the details of a custom image by using the CLI, use the ibmcloud is image command. Specify the name or ID of the custom image with the IMAGE variable.

ibmcloud is image IMAGE

For more information, see [ibmcloud is image](https://cloud.ibm.com/docs/vpc?topic=vpc-infrastructure-cli-plugin-vpc-referenceimage) in the VPC CLI reference page.





 Retrieving custom image details by using the API 

You can view the details of a custom image, such as name and ID, operating system and version, encryption status, deprecation or obsolescence dates, and assigned resource group, by using the application programming interface (API).
Your Code Engine application does not use this newer image because the newer image has a different digest than the digest of the image that is referenced by the application revision. Code Engine can still create new instances of the application revision if the image that was referenced originally still exists. If the originally referenced image by your application does not exist, Code Engine does not find the expected image digest, and the application fails because it cannot pull the image. Take care when you clean up and delete images, and when you configure retention policies for your container registry. Overwriting a tagged image is not problematic. However, problems can occur if you overwrite an image with an enabled retention policy that deletes the untagged image, or if you manually trigger a cleanup of untagged images.

If the error in the system events is similar to the following message, this error indicates that Code Engine cannot pull the image from the registry namespace. Check that the tag for your image points to the correct image digest.

Unable to pull the image. Image "<image_name>" does not exist in the registry namespace. Check your registry repository and tag. If the image exists in the repository, check whether the specified tag points to the correct image digest.

To use a newer image that was pushed with the same tag with your application, you must [update your application](https://cloud.ibm.com/docs/codeengine?topic=codeengine-update-app) to create a new application revision that references the newer tagged image.





 Next steps 

To learn more about troubleshooting images, see [Debugging images](https://cloud.ibm.com/docs/codeengine?topic=codeengine-troubleshoot-images).

For more information about troubleshooting apps, job, and builds with considerations for images, see the following topics.



* [Troubleshooting apps - Why is my app create failing?](https://cloud.ibm.com/docs/codeengine?topic=codeengine-ts-app-create-fails)
* [Troubleshooting apps - Why did my app stop running?]
You can make an immediate status change by using the ibmcloud is image-deprecate or ibmcloud is image-obsolete commands. You can also schedule these status changes for a future date and time by using the ibmcloud is image-update command. Specify the name or ID of the custom image with the IMAGE variable.

To make an immediate status change, use one of the following examples.

You can make an immediate status change only if a future status change is not scheduled. To remove a scheduled status change, see [Remove a scheduled custom image lifecycle status change by using the CLI](https://cloud.ibm.com/docs/vpc?topic=vpc-managing-custom-imagesschedule-reset-ilm-status-change-cli). After you remove the scheduled status change, you can make an immediate status change.



* Change the image lifecycle status to deprecate.

ibmcloud is image-deprecate IMAGE
* Change the image lifecycle status to obsolete.

ibmcloud is image-obsolete IMAGE



To schedule a status change, use the following example.

For the deprecate-at or obsolete-at option, specify a date in the ISO 8601 (YYYY-MM-DDThh:mm:ss+hh:mm) date and time format.



* YYYY is the four digit year
* MM is the two digit month
* DD is the two digit day
* T separates the date and time information
* hh is the two digit hours
* mm is the two digit minutes
* +hh:mm or -hh:mm is the UTC time zone



Thus, the date of 30 September 2023 at 8:00 p.m. in the North American Central Standard Time Zone (CST) would be 2023-09-30T20:00:00-06:00

When scheduling the date and time, you can't use your current date and time. For example, if it is 8 a.m. on June 12, then the scheduled date and time must be after 8 a.m. on June 12.