vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Failed to pull image "<image_name>": rpc error: code = Unknown desc = failed to pull and unpack image "<image_name:image_tag>": failed to resolve reference <image_name:image_tag>": pull access denied, repository does not exist or may require authorization: server message: insufficient_scope: authorization failed.
4. Code Engine cannot find your image in your container registry.

In this scenario, your image exists and the registry access works, but Code Engine finds a different image than the image it was expecting for a specific application revision. The container registry image digest does not match the expected digest of the image for an application revision.

When you deploy your application or new app revision, the latest version of your referenced container image is downloaded and deployed, unless a tag is specified for the image. If a tag is specified for the image, then the tagged image is used for the deployment.

If you create a newer version of the image with the same tag as the original image that was referenced by your application, the original image is overwritten in the container registry. However, Code Engine cannot find this newer image because the newer image has a different digest than the digest for the application revision. The image that is associated with your specific application revision has a unique container registry digest, and Code Engine uses this digest for the life of your application revision.

If you create a newer version of an image with the same tag as the original image, then the original image is overwritten in the container registry and becomes untagged. The newer image is tagged, and this newer image has a different digest. 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.
For more information about updating the scope of an image, see [Changing image scope](https://www.ibm.com/support/knowledgecenter/en/SSBS6K_3.2.0/manage_images/change_scope.html).

You can provide pipeline users with access to the base images (icr.io/continuous-delivery/pipeline/pipeline-base-image) that are used to run pipeline jobs, which are supplied by the global IBM Cloud Container Registry. To use these images, you must configure your pipeline jobs by using the Custom Dockerimage. You must also reference the expected image in the IBM Cloud® Private’s private registry, for example: mycluster.icp:8500/icr.io/continuous-delivery/pipeline/pipeline-base-image:latest.





 Can I manage private workers by using Terraform or APIs? 

You can use Terraform or APIs to add, update, or remove Delivery Pipeline private worker tool integrations in a toolchain. For more information about working with the Delivery Pipeline private worker tool integration, see [Working with tool integrations](https://cloud.ibm.com/docs/ContinuousDelivery?topic=ContinuousDelivery-integrations) and [Configuring Delivery Pipeline Private Worker](https://cloud.ibm.com/docs/ContinuousDelivery?topic=ContinuousDelivery-privateworker).

You cannot use Terraform or APIs to manage Delivery Pipeline private workers. Instead, use the console or the CLI to install, register, configure, and update private workers. For more information about these tasks, see [Installing Delivery Pipeline Private Workers](https://cloud.ibm.com/docs/ContinuousDelivery?topic=ContinuousDelivery-install-private-workers).
Deleting an image template 

Standard image templates can be deleted at any time after they are created.



  Before you begin 

First, go to the device menu and make sure that you have the correct account permissions to complete the tasks.



*  Go to your console's device menu. For more information, see [Navigating to devices](https://cloud.ibm.com/docs/image-templates?topic=virtual-servers-navigating-devices).
*  Make sure that you have any necessary account permissions and device access. Only the account owner, or a user with the Manage Users classic infrastructure permission, can adjust the permissions.



For more information about permissions, see [Classic infrastructure permissions](https://cloud.ibm.com/docs/account?topic=account-infrapermissioninfrapermission) and [Managing device access](https://cloud.ibm.com/docs/virtual-servers?topic=virtual-servers-managing-device-access).





  Deleting an image template 

Upon deletion, image templates cannot be retrieved and are wiped permanently from all data centers. Use the following steps to delete an image template.



1.  From the Devices menu, select Manage > Images.
2.  Click Actions for the image template that you want to delete and select Delete.
3.  Select Yes on the confirmation box to complete the deletion. Select No to cancel the deletion.



After an image template is deleted, the template is no longer available to use. All devices that were created by using the template remain available and fully functional. However, no additional devices can be created by using the deleted template. Image templates cannot be recovered after they are deleted.
* UI
* API







 Restoring a deprecated product or version 

After you deprecate your product or version, your software enters a 90-day deprecation period before it is removed from the IBM Cloud® catalog. During this deprecation period, you can't make changes to your product, but you can restore your software to its last published state to keep it in the catalog. Your software cannot be restored after the 90-day deprecation period.



 Restoring a deprecated product or version by using the console 

Complete the following steps to restore your product:



1. In the IBM Cloud console, click the Navigation Menu icon ![Navigation Menu icon](https://cloud.ibm.com/docs-content/v1/content/ff5860bfede49db3197c4bbba7f7123769bdc068/icons/icon_hamburger.svg) > Partner Center > Sell > My products.
2. Click the Actions icon ![Actions icon](https://cloud.ibm.com/docs-content/v1/content/ff5860bfede49db3197c4bbba7f7123769bdc068/icons/actions-icon-vertical.svg) for the product that you want to restore, and select Restore.



Complete the following steps to restore your version:



1. Go to the [Partner Center](https://cloud.ibm.com/partner-center/sell) in the IBM Cloud console, and click My products.
2. Select your product.
3. From the Software tab, click the Actions icon ![Actions icon](https://cloud.ibm.com/docs-content/v1/content/ff5860bfede49db3197c4bbba7f7123769bdc068/icons/actions-icon-vertical.svg) for the version you want to restore, and select Restore version.







 Restoring a deprecated product by using the API
Click Select custom image and select the image from volume that you created.









 Create an image from a volume with the CLI 

Use the CLI to create an image from a volume that is attached to an available virtual server instance as the primary boot volume or as a secondary boot volume.



 Before you begin 



1. Make sure that you downloaded, installed, and initialized the following CLI plug-ins:



* IBM Cloud CLI
* The infrastructure-service plug-in



For more information, see the [CLI Reference](https://cloud.ibm.com/docs/vpc?topic=vpc-infrastructure-cli-plugin-vpc-reference).

After you install the vpc-infrastructure plug-in, set the target to generation 2 by running the command ibmcloud is target --gen 2.
2. Make sure that you [created an IBM Cloud VPC](https://cloud.ibm.com/docs/vpc?topic=vpc-getting-started).







 Create an image from a boot volume that is attached to an instance 



1. To locate the instance that you want to create an image from, [list the instances](https://test.cloud.ibm.com/docs/vpc?topic=vpc-vpc-referenceinstances-list) in the region. Take note of the instance ID in the command output.



ibmcloud is instances



1. [Stop the running instance](https://cloud.ibm.com/docs/vpc?topic=vpc-infrastructure-cli-plugin-vpc-referenceinstance-stop) before you create the image from the volume.

ibmcloud is instance-stop INSTANCE_ID
2. Run the [image-create command](https://cloud.ibm.com/docs/vpc?topic=vpc-infrastructure-cli-plugin-vpc-referenceimage-create) to create an image of a boot volume. Specify the ID of the source volume.

ibmcloud is image-create IMAGE_NAME [--source-volume VOLUME_ID]

Example:
To remove a specific tag from an image and leave the underlying image and any other tags in place, use the ibmcloud cr image-untag command. If you want to delete the underlying image, and all its tags, use the [ibmcloud cr image-rm](https://cloud.ibm.com/docs/Registry?topic=Registry-containerregclibx_cr_image_rm) command instead.

ibmcloud cr image-untag IMAGE [IMAGE...]



 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 

IMAGE
: The name of the image for which you want to remove the tag. You can delete the tag from multiple images at the same time by listing each image in the command with a space between each name. IMAGE must be in the format repository:tag, for example, us.icr.io/namespace/image:latest.

To find the names of your images, run ibmcloud cr image-list. Combine the content of the Repository column (repository) and Tag column (tag) separated by a colon (:) to create the image name in the format repository:tag. If a tag is not specified in the image name, the command fails.





 Example 

Remove the tag 1 from the image us.icr.io/birds/bluebird:1.

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







 ibmcloud cr info 

Displays the name and the account of the registry that you are logged in to.

ibmcloud cr info



 Prerequisites 

None







 ibmcloud cr login 

Log the local Docker or Podman client in to IBM Cloud Container Registry.

This command is required if you want to run the push or pull commands for the registry. If you want to run other ibmcloud cr commands, you're not required to log in to Container Registry.

ibmcloud cr login [--client CLIENT]
Managing images from the Image Templates page 

The Image Templates page in the IBM Cloud® console displays all of the images that are associated with an account. From the Image Templates page, you can interact with images and import new images that are stored on existing Object Storage accounts.



  Before you begin 

First, go to the device menu and make sure that you have the correct account permissions to complete the tasks.



*  Go to your console's device menu. For more information, see [Navigating to devices](https://cloud.ibm.com/docs/image-templates?topic=virtual-servers-navigating-devices).
*  Make sure that you have any necessary account permissions and device access. Only the account owner, or a user with the Manage Users classic infrastructure permission, can adjust the permissions.



For more information about permissions, see [Classic infrastructure permissions](https://cloud.ibm.com/docs/account?topic=account-infrapermissioninfrapermission) and [Managing device access](https://cloud.ibm.com/docs/virtual-servers?topic=virtual-servers-managing-device-access).





  Managing images from the Image Templates page 

Access the Image Templates page by selecting Devices > Manage > Images.

On the Image Templates page, you see all of the private images that are associated with the account. Any interactions with private images happen here. You can drag columns to customize the view. You can also access public images by clicking the Private Images drop-down selector and choosing Public Images instead.

From the Image Templates page, you can order a virtual server from a standard image, delete private images, and import or export images.
When you update an image, you must provide all environment variables (including the variables that you set previously).

In this description "environment variables" are not set as environment variables, instead they provided within /.runqenv. For information about environment variables, see [Configuring your server](https://cloud.ibm.com/docs/hp-virtual-servers?topic=hp-virtual-servers-byoibyoi_config).

Example with one environment variable:

ibmcloud hpvs instance-update (NAME | CRN) -i latest -e name=value

Example with multiple environment variables:

ibmcloud hpvs instance-update (NAME | CRN) -i latest -e name1=value1 -e name2=value2
Restore a deleted image from the trash. You can choose to restore by [tag](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_overviewoverview_elements_tag) or by [digest](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_overviewoverview_elements_digest). If you restore by digest, the digest and all its tags in the same repository are restored. To find out what is in the trash, run the [ibmcloud cr trash-list](https://cloud.ibm.com/docs/Registry?topic=Registry-containerregclibx_cr_trash_list) command.

If you get an error when you're restoring an image that says that the tagged image exists, see [Why do I get an error when I'm restoring an image?](https://cloud.ibm.com/docs/Registry?topic=Registry-troubleshoot-image-restore) for assistance.

If you're restoring an image by digest, but some tags aren't restored, see [Why aren't all the tags restored when I restore by digest?](https://cloud.ibm.com/docs/Registry?topic=Registry-troubleshoot-image-restore-digest) for assistance.

ibmcloud cr image-restore IMAGE



 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 

IMAGE
: The name of the image that you want to restore from the trash.

To find the names of your images in the trash, run the ibmcloud cr trash-list command.

You can identify images by using either the tag or the digest. The image to restore can be referenced by digest <dns>/<namespace>/<repo>@<digest>, which restores the digest and all its tags in the same repository, or by tag <dns>/<namespace>/<repo>:<tag>.
(https://cloud.ibm.com/docs/Registry?topic=Registry-troubleshoot-image-restore-digest) for assistance.

ibmcloud cr image-restore IMAGE



 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 

IMAGE
: The name of the image that you want to restore from the trash.

To find the names of your images in the trash, run the ibmcloud cr trash-list command.

You can identify images by using either the tag or the digest. The image to restore can be referenced by digest <dns>/<namespace>/<repo>@<digest>, which restores the digest and all its tags in the same repository, or 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.

Images are stored in the trash for 30 days.





 Example 

To restore the image us.icr.io/birds/bluebird:1, run the following command.

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

For more information about how to use the ibmcloud cr image-restore command, see [Restoring images](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_images_registry_images_restore).







 ibmcloud cr image-rm 

Delete one or more specified images from Container Registry. You can reference the image that you want to delete either by [digest](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_overviewoverview_elements_digest) or by [tag](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_overviewoverview_elements_tag).
Complete the required information for importing your VHD image, and select the Your License checkbox that is shown near the Operating System dropdown box. For more information about importing images, see [Preparing and importing images](https://cloud.ibm.com/docs/image-templates?topic=image-templates-preparing-and-importing-imagespreparing-and-importing-images).







 Updating an image template to specify a user provided OS license 

If you have an existing VHD image template, you can specify that you want to provide your own license or subscription for the operating system.

To access an image template and signal that it uses your own existing license or subscription, complete the following steps:



1. From the Devices menu, select Manage > Images.
2. From the list of templates, click the image template name that you want to update.
3. On the Image Template Details page, select the User Provided checkbox under the OS License heading, and click Update.
![del-view-archived.png](https://cloud.ibm.com/docs-content/v1/content/78bb71851d95d7580503eb9ba10cf3ae31490ade/apiconnect/tutorials/images/del-view-archived.png)
9. Click the vertical ellipsis on the Weather Provider API 2.0.0 line.
![del-prod-list5.png](https://cloud.ibm.com/docs-content/v1/content/78bb71851d95d7580503eb9ba10cf3ae31490ade/apiconnect/tutorials/images/del-prod-list5.png)
10. Select Unarchive.
![del-unarchive.png](https://cloud.ibm.com/docs-content/v1/content/78bb71851d95d7580503eb9ba10cf3ae31490ade/apiconnect/tutorials/images/del-unarchive.png) The product state changes to Retired. ![del-prod-list6.png](https://cloud.ibm.com/docs-content/v1/content/78bb71851d95d7580503eb9ba10cf3ae31490ade/apiconnect/tutorials/images/del-prod-list6.png)







 Conclusion 

In this tutorial, you completed the following activities:



1. Deleted an API Product
2. Retired an API Product
3. Archived an API Product
4. Unarchived an API Product
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. Combine the content of the Repository column (repository) and Tag column (tag) separated by a colon (:) to create the image name in the format repository:tag.



If you get a manifest error when you try to tag your image, see [Why do I get a manifest type error when I tag my image?](https://cloud.ibm.com/docs/Registry?topic=Registry-troubleshoot-manifest-error-type), [Why do I get a manifest version error?](https://cloud.ibm.com/docs/Registry?topic=Registry-troubleshoot-manifest-error-version), and [Why do I get a manifest list invalid error?](https://cloud.ibm.com/docs/Registry?topic=Registry-troubleshoot-manifest-list-error) for assistance.

ibmcloud cr image-tag [SOURCE_IMAGE] [TARGET_IMAGE]



 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 

SOURCE_IMAGE
: The name of the source image. You can identify source images by using either the digest <dns>/<namespace>/<repo>@<digest> or by tag <dns>/<namespace>/<repo>:<tag>.
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.



The date for obsolescence must be after the deprecation date.
5. Click Schedule.







 Change the custom image lifecycle status by using the CLI 

You can change the lifecycle status of an IBM Cloud VPC custom image by using the command-line interface (CLI). 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.
* [Removing tags from images in your private repository](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_images_registry_images_untag)
* [Deleting images from your private repository](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_images_registry_images_remove)



* [Deleting images from your private repository in the CLI](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_images_registry_images_remove_cli)
* [Deleting images from your private repository in the console](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_images_registry_images_remove_gui)



* [Listing images in the trash](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_images_registry_images_list_trash)
* [Restoring images](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_images_registry_images_restore)



* [Restoring images by digest](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_images_registry_images_restore_digest)
* [Restoring images by tag](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_images_registry_images_restore_tag)



* [Deleting a private repository and any associated images](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_images_registry_repo_remove)







 Using Helm charts 

[Using Helm charts](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_helm_chartsregistry_helm_charts)



* [OCI support for Helm charts](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_helm_chartsregistry_helm_charts_oci)