vania-janet/multiturn-rag-retrieval-data huggingface dataset:
image is.image.image.delete Image was deleted 
 image is.image.image.update Image was updated 
 image is.image.image.read Image was retrieved 
 image is.image.image.export Image was exported 
 image is.image.image-export-job.create Image export job was created 
 image is.image.image-export-job.delete Image export job was deleted 
 image is.image.image-export-job.update Image export job was updated 
 image is.image.image-export-job.read Image export job was retrieved 
 image is.image.image-export-job.list Image export jobs were listed 



For the image update event, if you are rotating the root key for an image, the CRN for the old key and new key remains the same. The ID for the new key that is rotated in is indicated in the kmsKeyRefID field of the image.





 Placement group resources 

The following table lists the actions that are related to placement group resources and the generation of events.



Table 21. Actions that generate events for placement group resources

 Resource Action Description 

 placement_group is.placement-group.placement-group.create Placement group was created 
 placement_group is.placement-group.placement-group.delete Placement group was deleted 
 placement_group is.placement-group.placement-group.update Placement group was updated 
 instance is.instance.instance.create Instance was created and includes a placement group reference 
 instance is.instance.instance.update Instance was updated and includes updates to the placement group reference 









 Storage resources 



 Block storage events 

The following table lists the actions that are related to volume resources and the generation of events.



Table 22. Actions that generate events for block storage resources

 Resource Action Description 

 volume is.volume.volume.create Volume was created 
 volume is.volume.volume.update Volume was updated 
 volume is.volume.volume.delete Volume was deleted 
 volume is.volume.volume.read One or more volumes were retrieved 
 volume is.volume.volume.operate Volume ID was specified 



An event does not contain a volume name if no information is available at the time of the event.
Creating, editing, and deleting compute images (ibmcloud sl image) 

Use the following commands from the IBM Cloud® Command Line Interface to manage IBM Cloud compute images.



  ibmcloud sl image delete 

Delete an image:

ibmcloud sl image delete IDENTIFIER

Examples:

ibmcloud sl image delete 12345678

This command deletes image with ID 12345678.





  ibmcloud sl image detail 

Get details for an image:

ibmcloud sl image detail IDENTIFIER

Examples:

ibmcloud sl image detail 12345678

This command gets details for image with ID 12345678.





  ibmcloud sl image edit 

Edit the details of an image:

ibmcloud sl image edit IDENTIFIER [OPTIONS]

Command options:

--name
:   Name of the image.

--note
:   Add notes for the image.

--tag
:   Tags for the image.

Examples:

ibmcloud sl image edit 12345678 --name ubuntu16 --note testing --tag staging

This command edits an image with ID 12345678 and set its name to ubuntu16, note to testing, and tag to staging.





  ibmcloud sl image list 

List all images on your account:

ibmcloud sl image list [OPTIONS]

Command options:

--name
:   Filter on image name.

--public
:   Display only public images.

--private
:   Display only private images.

Examples:

ibmcloud sl image list --public

This command list all public images on current account.
If you have a running container that uses a previous version of your Docker image, any new invocations continue to use that image. You must run the update command so that new invocations begin running on the new image.
3. Update an action and include the local path to your app or the Docker image.

ibmcloud fn action update <action_name> <app_file> --kind <runtime>

Example

ibmcloud fn action update hello hello.js --kind nodejs:10

Example output

ok: updated action hello

If you packaged your code as a Docker image, include --docker <docker_hub_username>/<docker_hub_image>:<tag> with your create command instead of the path to the local app and the --kind flag. Manage your images well by not using the latest tag whenever possible. When the latest tag is used, the image with that tag is used, which might not always be the most recently created image.

ibmcloud fn action update hello --docker <docker_hub_username>/<docker_hub_image>:<tag>







 Updating actions from the console 

You can update your actions directly from the Actions page.



1. From the [IBM Cloud Functions Actions ![External link icon](https://cloud.ibm.com/docs-content/v1/content/adc643f3bedeea02b638bc1c34732852dcb40a45/icons/launch-glyph.svg)](https://cloud.ibm.com/functions/actions) page, search for the action that you want to change.
2. From the overflow menu for that action, select Manage Action.
3. Edit your code by toggling between Edit and View modes. You can test your code by clicking Invoke.
4. Change your runtime by selecting Runtime from the navigation menu and selecting your new runtime.
5. When you are finished making changes, save your action.









 Binding parameters to actions
On the Image details page, click the Export history tab.





 Deleting or canceling an image export job by using the UI 

To delete a completed image export job or cancel (and delete) an in-progress image export job, complete the following steps.



1. On the image details page, click the Export history tab.
2. For the export job that you want to delete or cancel, click the Actions icon ![More Actions icon](https://cloud.ibm.com/docs-content/v1/content/f02b9c9adcbb7328d95a45e105cec371d50f15eb/icons/action-menu-icon.svg) and select Delete.







 Renaming an image export job by using the UI 

To rename an image export job, complete the following steps.



1. On the image details page, click the Export history tab.
2. For the export job that you want to rename, click the Actions icon ![More Actions icon](https://cloud.ibm.com/docs-content/v1/content/f02b9c9adcbb7328d95a45e105cec371d50f15eb/icons/action-menu-icon.svg) and select Rename.









 Viewing custom image export history by using the CLI 

To view the export history of a specific custom image by using the CLI, use the ibmcloud is image-export-jobs command. Specify the name or ID of the custom image that was exported by using the IMAGE variable.

ibmcloud is image-export-jobs IMAGE

The following example shows the export job history for a custom image with the ID of 72251a2e-d6c5-42b4-97b0-b5f8e8d1f479.

ibmcloud is image-export-jobs 72251a2e-d6c5-42b4-97b0-b5f8e8d1f479
* [What tools can I use to build and push images?](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_faqfaq_tools)
* [How many namespaces can you have?](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_faqfaq_namespace)
* [Can I rename a namespace?](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_faqfaq_namespace_rename)
* [Do images in the trash count toward my quota?](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_faqfaq_trash)
* [How do I find the image digest?](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_faqfaq_digest)
* [How do I use digests to work with images?](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_faqfaq_digest_use)
* [How do you use access control?](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_faqfaq_access_control)
* [How can I share an image with many users?](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_faqfaq_share_image)
* [Do I have any untagged images?](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_faqfaq_untagged_image_1)
* [Do I need untagged images?](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_faqfaq_untagged_image_2)
* [What are eligible images?]
When you run a Docker command and do not specify the tag of a repository image, then the image tagged latest is used by default.





 Untagged image 

An image that has no

tagis an untagged image. Images that are untagged can be referenced by using the digest reference format <repository>@<digest> as opposed to the tag reference format <repository>:<tag>. Untagged images are typically the result of an image that is pushed with a pre-existing <repository>:<tag> combination. In this case, the tag is overwritten and the original image becomes untagged.

You can view untagged images by using the [ibmcloud cr image-digests](https://cloud.ibm.com/docs/Registry?topic=Registry-containerregclibx_cr_image_digests) command, and clean up untagged images by using the [ibmcloud cr image-prune-untagged](https://cloud.ibm.com/docs/Registry?topic=Registry-containerregcliic_cr_image_prune_untagged) command.







 Regions 

The default instance of Container Registry is the global registry. The global registry doesn't include a region in its [domain name](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_overviewoverview_elements_domain_name) (icr.io).

Use the global instance of the registry unless you have a specific requirement, for example, data sovereignty, to store your data in a particular region. 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).
image=$(ibmcloud is images | grep -i "debian.available.amd64.public" | cut -d" " -f1)

Save the image ID as a variable, which is used later to provision an instance.



* Select an image shared from a private catalog for the instance



To list all available images, run the following command.

ibmcloud is catalog-image-offerings

This command returns both the offering_crn and the offering_version_crn for the available images. When you create an instance, you can either provision an instance from the private catalog image at the latest version in a catalog product offering by using the offering_crn or from a specific version in the catalog product offering by using the offering_version_crn.

Save the offering_crn and offering_version_crnin variables, which is used later to provision an instance.

offering_crn="crn:v1:staging:public:globalcatalog-collection:global:a/efe5afc483594adaa8325e2b4d1290df:0b322820-dafd-4b5e-b694-6465da6f008a:offering:136559f6-4588-4af2-8585-f3c625eee09d"
offering_version_crn="crn:v1:staging:public:globalcatalog-collection:global:a/efe5afc483594adaa8325e2b4d1290df:0b322820-dafd-4b5e-b694-6465da6f008a:version:136559f6-4588-4af2-8585-f3c625eee09d/8ae92879-e253-4a7c-b09f-8d30af12e518"



After you know these values, use them to run the instance-template-create command. In addition to the information that you gathered, you must specify a name for the instance.
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-images&interface=uicustom-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).
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. The previous dates and times are replaced with the new dates and times.







 Removing previously scheduled image from volume lifecycle statuses by using the API 

Make a PATCH /images request to remove any scheduled status change by updating deprecation_at or obsolescence_at to null. This property change removes the date and time from the image and the image is no longer scheduled for that status change.



* To change an image from deprecated to available, change the deprecation_at property to null.
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.

For more information, see [Removing tags from images in your private repository](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_images_registry_images_untag).





 13 May 2019 

End of support for Container Scanner
: Container Scanner is now deprecated and is no longer usable.





 2 April 2019 

General Availability of Container Image Security Enforcement
: Use Container Image Security Enforcement to verify your container images before you deploy them to your cluster in IBM Cloud Kubernetes Service. You can control where images are deployed from, enforce Vulnerability Advisor policies, and ensure that [content trust](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_trustedcontent) is properly applied to the image.





 14 March 2019 

IBM Cloud Activity Tracker available for Container Registry
: Use the IBM Cloud Activity Tracker service to track how users and applications interact with the Container Registry service in IBM Cloud.

For more information, see [Auditing events for Container Registry](https://cloud.ibm.com/docs/Registry?topic=Registry-at_events).





 25 February 2019 

New domain names
: Container Registry is adopting new domain names. The new domain names are available in the IBM Cloud console and the CLI. You can use the new icr.io domain names now. The existing registry.bluemix.net domain names are deprecated, but you can continue to use them until the end of support date. An end of support date is not available yet.

For more information, see [Regions](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_overviewregistry_regions) and [Introducing New IBM Cloud Container Registry Domain Names](https://www.ibm.com/cloud/blog/announcements/introducing-new-ibm-cloud-container-registry-domain-names).
[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, locate the image that you want to delete. From the overflow menu (ellipsis), select Delete.







 Deleting an image from volume by using the CLI 



1. Locate the image from volume in the list of images.

ibmcloud is images
2. Delete the image by ID.

ibmcloud is image-delete IMAGE_ID







 Deleting an image from volume by using the API 

Specify a DELETE/images call and specify the ID of the image that was created from the boot volume.



1. Locate the ID of the image from volume:

GET/images
2. Delete the image by ID:

DELETE/image/{image_id}







 Next steps 

Preview the end-to-end process for creating an image from volume, then you can use the image when you create a new virtual server instance. For more information, see the [Image from volume tutorial](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-and-using-an-image-from-volume).
* [Updating an app to reference a different image in Container Registry with the CLI](https://cloud.ibm.com/docs/codeengine?topic=codeengine-update-appupdate-app-crimage-cli)
* [Updating an app to reference an image that is built from source code from the console](https://cloud.ibm.com/docs/codeengine?topic=codeengine-update-appupdate-app-source-console)
* [Updating an app to reference an image that is built from source code with the CLI](https://cloud.ibm.com/docs/codeengine?topic=codeengine-update-appupdate-app-source-cli)





[Configuring custom domain mappings for your app](https://cloud.ibm.com/docs/codeengine?topic=codeengine-domain-mappingsdomain-mappings)



* [Considerations before you use custom domain mappings in Code Engine](https://cloud.ibm.com/docs/codeengine?topic=codeengine-domain-mappingsconsiderations-custom-domain)
* [Preparing to add a custom domain mapping](https://cloud.ibm.com/docs/codeengine?topic=codeengine-domain-mappingsprepare-custom-domain)



* [How can I obtain a certificate for my custom domain?](https://cloud.ibm.com/docs/codeengine?topic=codeengine-domain-mappingsprepare-custom-domain-cert)
* [Can I use Cloud Internet Services (CIS) for domain management when I am using custom domain mapping with Code Engine?](https://cloud.ibm.com/docs/codeengine?topic=codeengine-domain-mappingsprepare-use-cis)



* [Configuring custom domain mappings](https://cloud.ibm.com/docs/codeengine?topic=codeengine-domain-mappingscustom-domain)
To identify the image, list the contents of the trash by running the [ibmcloud cr trash-list](https://cloud.ibm.com/docs/cli?topic=cli-containerregclibx_cr_trash_list) command and restore the selected image by running the [ibmcloud cr image-restore](https://cloud.ibm.com/docs/cli?topic=cli-containerregclibx_cr_image_restore) command.

If you want to cancel a retention policy, see [Update a retention policy to keep all your images](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_retentionretention_policy_keep).

ibmcloud cr retention-policy-set [--retain-untagged] --images IMAGECOUNT NAMESPACE



 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 

NAMESPACE
: The namespace for which you want to create a policy.

--retain-untagged
: (Optional) Retain all untagged images when the retention policy is being processed. Only tagged images are analyzed and, if the images don't meet the criteria, they are deleted. If the option isn't specified, all tagged and untagged images are analyzed and, if the images don't meet the criteria, they are deleted.

--images
: Determines how many images to keep within each repository in the specified namespace. The newest images are retained. The age of images is determined by their build date. IMAGECOUNT is the number of images that you want to retain in each repository for the namespace. To return a policy to the default state that keeps all the images, set IMAGECOUNT to All.





 Examples 

Set a policy that retains the newest 20 images within each repository in the namespace birds.

ibmcloud cr retention-policy-set --images 20 birds
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, 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 image that is referenced by the application revision. Code Engine can still create new instances of the application revision as long as the untagged image, which was referenced originally, still exists. For more information, see [Why can't Code Engine pull an image?](https://cloud.ibm.com/docs/codeengine?topic=codeengine-image-cannot-pull)



 Updating an app to reference a different image in Container Registry from the console 

Update an application to reference a different image in a container registry by using the Code Engine console.

For this example, let's update the helloapp that you created in [Deploying an application that references an image in a container registry from the console](https://cloud.ibm.com/docs/codeengine?topic=codeengine-deploy-app-crimagedeploy-app-crimage-console) to reference a different image. The updated app references the helloworld_repo image in the mynamespace2 namespace in Container Registry. The following steps describe adding access to a registry during the update of an app.

For more information about adding an image to Container Registry, see [Getting started with IBM Cloud Container Registry](https://cloud.ibm.com/docs/Registry?topic=Registry-getting-startedgetting-started).



1. Navigate to your application page. One way to navigate to your application page is to



* Locate the [Code Engine Projects page](https://cloud.ibm.com/codeengine/projects).
* Click the name of your project to open the Overview page.
* Click Applications to open a list of your applications. Click the name of your application to open the application page.
to access the list of options.
2. Click Configure Pipeline.
3. In the Image version tab, select either the Experimental: RedHat UBI or the Ubuntu image type. Then, based on the selected image type, select the default image version to use for all jobs in your pipeline. You can also customize this setting for each job in each stage of your pipeline.



Zoom

![Image version](https://cloud.ibm.com/docs-content/v1/content/562806c0b18119f4d21cb66f5ae6d051634b4a16/ContinuousDelivery/images/ubi-ubuntu-vbi.png)

Figure 1. Image version

If you choose the Latest option, the pipeline jobs are run with the current image version. The current image version is displayed in brackets after the Latest option. When a new image version is available, the image that is used changes. You might need to modify your pipeline to support any newer tools that are included in the new image.

Ubuntu based versioned based images are tagged as 2.x versions. Red Hat UBI based versioned base images are tagged as 3.x versions.

To add tools in a Red Hat UBI-based image, you must use the yum command. apt-get or apt commands are exclusively reserved for Ubuntu images. Because of these command restrictions, you cannot update existing pipelines to use version 3.x images without modifying the scripts.





 Image version contents 

After version 2.0, images no longer include grunt or python. If these tools are required for your build, you can install them manually. To install grunt, run npm install -g grunt-cli. Make sure that you don't change the Node.js version after you install grunt. To install python on a 2.x vbi, run apt-get -qq update && apt-get -qq install -y python.