vania-janet/multiturn-rag-retrieval-data huggingface dataset:
[Menu icon](https://cloud.ibm.com/docs-content/v1/content/8aa0853d34cf2349f1d2db8e5c61e6422a580169/cloud-infrastructure/includes/icons/icon_hamburger.svg) > Classic Infrastructure > Devices > Device List > Manage > Images.
2. Locate the image template that you created in Evaluate and create an image template.
3. Click the Actions![Menu icon](https://cloud.ibm.com/docs-content/v1/content/8aa0853d34cf2349f1d2db8e5c61e6422a580169/cloud-infrastructure/icons/action-menu-icon.svg) icon for the image template and select Order < Type of > VSI. < Type of > is the type of virtual server that you are creating.
4. Change the virtual server location to the new data center. The form defaults to the original virtual server properties. Other than selecting the new location, you can keep or modify the rest of the parameters to better suit the new environment, for example:



* Enter hostname and domain
* (Optional) Select or create a placement group
* Select a virtual server profile
* (Recommended) Select SSH key
* Select Uplink port speeds





The new virtual server is automatically given a new IP address on deployment.





 Verify and validate the virtual server, and update network resources 



1. After the new virtual server is deployed, verify the virtual server.
2. Make any OS level modifications that are needed to the virtual server.
3. (Optional) If block or file storage volumes were part of the original virtual server, create the new volumes and update the iSCSI or NFS configuration on the new virtual server. After created and attached, copy the data over from the old to new virtual server by using your tool of choice.
4. Update and add or modify any infrastructure resources, such as:



* Security groups
* Firewall rules
* Load balancers
* VPN
* DNS









 Final check
Importing a custom image 

You can create a bare metal server by using an imported image template. The new bare metal servers have the same configurations that are included in the imported custom image template.

Follow these steps to import a custom image.



1.  Go to Devices > Manage > Images and click Import custom image.
2.  Enter an image name and the IBM API key for the image that you want to import.
3.  Click the name of the image that you want to import, accept the Third-Party Service Agreements, and click Import custom image.
If it takes longer, [cancel the image creation](https://cloud.ibm.com/docs/vpc?topic=vpc-image-from-volume-vpc-manageifv-delete-queued).





 Cancelling an image that is queued for creation 

You can cancel the image creation by deleting the image if the underlying job didn't start yet. For images in a pending state, the GET/images API call returns an image_request_queued reason code. You can delete the pending image with DELETE/image{image_id}. Alternatively, you can use the [UI](https://cloud.ibm.com/docs/vpc?topic=vpc-image-from-volume-vpc-manageifv-delete-ui) or [CLI](https://cloud.ibm.com/docs/vpc?topic=vpc-image-from-volume-vpc-manageifv-delete-cli) to delete the image that is in a pending state.







 Deleting an image from volume by using the UI 

Delete an image from a volume from the list of custom images. You can delete images in that are [while they are being created](https://cloud.ibm.com/docs/vpc?topic=vpc-image-from-volume-vpc-manageifv-delete-queued) (pending state) and available images.



1. Go to the list of custom images. In the [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, locate the image that you want to delete. From the overflow menu (ellipsis), select Delete.
You can identify images by using either the digest <dns>/<namespace>/<repo>@<digest> 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.

To find the names of your images, run one of the following commands:



* 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 a tag is not specified in the image name, the image that is tagged latest is deleted by default.







 Example 

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.
By using this interface, the default built-in GPG Image signing will be able to pick up these images and process them.







 Loading image artifacts 

At the end of the pipeline in the release stage, you can access these artifacts using the pipelinectl interface:

list_artifacts
load_artifact <image-alias> <property>

list_artifacts lists the image aliases available, where <property> is any property that you or the pipeline added previously. Using these together you can iterate over your artifacts, for example:

list_artifacts | while IFS= read -r artifact; do

$image=$(load_artifact "$artifact" name)
$digest=$(load_artifact "$artifact" digest)
$signature=$(load_artifact "$artifact" signature)

 update your inventory using these

done

The signature property is added by the default built-in GPG Image signing task.

For more information, check out the following documentation:



* [Documentation on stages for user-defined scripts](https://cloud.ibm.com/docs/devsecops?topic=devsecops-custom-scripts)
* [API documentation for pipelinectl](https://cloud.ibm.com/docs/devsecops?topic=devsecops-cd-devsecops-pipelinectl)
* [The default built-in GPG Image sign script](https://us-south.git.cloud.ibm.com/open-toolchain/hello-compliance-app/-/blob/master/scripts/sign_image.sh)
(https://cloud.ibm.com/docs/Registry?topic=Registry-ts-app-image-pull)









 Troubleshooting CLI commands 

Troubleshoot CLI command problems.



* [Why can't I add a namespace?](https://cloud.ibm.com/docs/Registry?topic=Registry-troubleshoot-add-namespace)
* [When I create a namespace, why aren't I authorized to access the specified resource?](https://cloud.ibm.com/docs/Registry?topic=Registry-troubleshoot-namespace-auth)
* [Why can't I find my image or my namespace?](https://cloud.ibm.com/docs/Registry?topic=Registry-troubleshoot-image-find)
* [Why don't all my namespaces show in the Resource list?](https://cloud.ibm.com/docs/Registry?topic=Registry-troubleshoot-namespace-resource-list)
* [Why is it timing out when I list images?](https://cloud.ibm.com/docs/Registry?topic=Registry-troubleshoot-image-timeout)
* [Why can't I pull the newest image by using the latest tag?](https://cloud.ibm.com/docs/Registry?topic=Registry-troubleshoot-docker-latest)
* [Why do all the tags get deleted when I delete an image?](https://cloud.ibm.com/docs/Registry?topic=Registry-troubleshoot-image-rm)
* [Why doesn't the retention command show all the images?](https://cloud.ibm.com/docs/Registry?topic=Registry-troubleshoot-image-list-retention)
* [Why do I get an error when I'm restoring an image?](https://cloud.ibm.com/docs/Registry?topic=Registry-troubleshoot-image-restore)
* [Why aren't all the tags restored when I restore by digest?]
Specify the name or ID of the image export job by using the JOB variable.

ibmcloud is image-export-job-delete IMAGE JOB

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





 Renaming an image export job by using the CLI 

To rename a custom image export job by using the CLI, use the ibmcloud is image-export-job-update command. Specify the name or ID of the custom image that was exported by using the IMAGE variable. Specify the name or ID of the image export job by using the JOB variable. Specify the new name that you want to assign to the image export job by using the NAME variable.

ibmcloud is image-export-job-update IMAGE JOB --name NAME

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





 Viewing custom image export history by using the API 

To view the export history of a specific custom image by using the API, use [List all image export jobs](https://cloud.ibm.com/apidocs/vpc/latestlist_image_export_jobs).

For the$image_id variable, specify the ID of the custom image for which you want to display export jobs.

curl -X GET "$vpc_api_endpoint/v1/images/$image_id/export_jobs?version=2022-11-21&generation=2" -H "Authorization: Bearer $iam_token"





 Viewing image export job details by using the API 

To view the details of a specific image export job by using the API, use [Retrieve an image export job](https://cloud.ibm.com/apidocs/vpc/latestget-image-export-job).
curl "$SERVICE_URL/users/_design/allusers?rev=1-e23b9e942c19e9fb10ff1fde2e50e0f5" 	-X COPY 	-H "Content-Type: application/json" 	-H "Destination: _design/copyOfAllusers"





 Copying to an existing design document 

To overwrite or copy to an existing document, specify the current revision string for the target document by using the rev parameter to the Destination HTTP Header string.

See the following example command to overwrite an existing copy of the design document by using HTTP:

COPY $SERVICE_URL/$DATABASE/_design/$DDOC
Content-Type: application/json
Destination: _design/$COPY_OF_DDOC?rev=$REV

See the following example command to overwrite an existing copy of the design document by using the command line:

curl "$SERVICE_URL/users/_design/allusers" 	-X COPY 	-H "Content-Type: application/json" 	-H "Destination: _design/copyOfAllusers?rev=1-9c65296036141e575d32ba9c034dd3ee"

The return value is the ID and new revision of the copied document.

See the following example response to overwrite an existing copy of the design document:

{
"id" : "_design/copyOfAllusers",
"rev" : "2-55b6a1b251902a2c249b667dab1c6692"
}







 Deleting a design document 

You can delete an existing design document. Deleting a design document also deletes all of the associated view indexes, and recovers the corresponding space on disk for the indexes in question.

To delete a design document successfully, you must specify the current revision of the design document by using the rev query argument.

See the following example command to delete a design document by using HTTP:
"resources": [
{
"type": "application/vnd.ibm.kms.key+json",
"id": "02fd6835-6001-4482-a892-13bd2085f75d",
"name": "test-root-key",
"state": 1,
"extractable": false,
"crn": "crn:v1:bluemix:public:kms:us-south:a/f047b55a3362ac06afad8a3f2f5586ea:12e8c9c2-a162-472d-b7d6-8b9a86b815a6:key:02fd6835-6001-4482-a892-13bd2085f75d",
"imported": false,
"creationDate": "2020-03-12T03:50:12Z",
"createdBy": "...",
"algorithmType": "Deprecated",
"algorithmMetadata": {
"bitLength": "256",
"mode": "Deprecated"
},
"algorithmBitSize": 256,
"algorithmMode": "Deprecated",
"lastUpdateDate": "2020-03-12T03:50:12Z",
"lastRotateDate": "2020-03-12T03:49:01Z",
"keyVersion": {
"id": "2291e4ae-a14c-4af9-88f0-27c0cb2739e2",
"creationDate": "2020-03-12T03:50:12Z"
},
"dualAuthDelete": {
"enabled": false
},
"deleted": false
}
]
}
[Available](https://cloud.ibm.com/docs-content/v1/content/11f96f96f8f4b60cf6f3fa4d904856a2c4528bc2/icons/checkmark-icon.svg) ![Available](https://cloud.ibm.com/docs-content/v1/content/11f96f96f8f4b60cf6f3fa4d904856a2c4528bc2/icons/checkmark-icon.svg) 
 vApp: VM Migrate, Force Undeploy, Relocate, Consolidate ![Available](https://cloud.ibm.com/docs-content/v1/content/11f96f96f8f4b60cf6f3fa4d904856a2c4528bc2/icons/checkmark-icon.svg) ![Available](https://cloud.ibm.com/docs-content/v1/content/11f96f96f8f4b60cf6f3fa4d904856a2c4528bc2/icons/checkmark-icon.svg) ![Available](https://cloud.ibm.com/docs-content/v1/content/11f96f96f8f4b60cf6f3fa4d904856a2c4528bc2/icons/checkmark-icon.svg) 
 VCD Extension: Register, Unregister, Refresh, Associate or Disassociate ![Available](https://cloud.ibm.com/docs-content/v1/content/11f96f96f8f4b60cf6f3fa4d904856a2c4528bc2/icons/checkmark-icon.svg) !
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. Encrypted custom images are identified by a lock icon after the image name. You can select from the following actions:





Table 1. Custom image actions

 Action Description 

 Rename Rename the custom image. 
 Create virtual server instance Create a new virtual server from the custom image. 
 Export Copy the custom image to IBM Cloud Object Storage. 
 Share to catalog Share the IBM Cloud VPC custom image to an existing private catalog. 
 Copy Copy the UUID of the custom image. 
 View checksum View the checksum for the custom image. 
 Schedule lifecycle Opens the Schedule image lifecycle panel. You can make an immediate status change or schedule a statue change for a future date and time. 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.
You can identify source images by using either the digest <dns>/<namespace>/<repo>@<digest> 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.

TARGET_IMAGE
: The name of the target image. TARGET_IMAGE must be in the format repository:tag, for example, us.icr.io/namespace/image:latest.





 Examples 

Add another tag reference, latest, to the image us.icr.io/birds/bluebird:1.

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

Copy the image us.icr.io/birds/bluebird:peck to another repository in the same namespace birds/pigeon.

ibmcloud cr image-tag us.icr.io/birds/bluebird:peck us.icr.io/birds/pigeon:peck

Copy the image us.icr.io/birds/bluebird:peck to another namespace animals to which you have access.

ibmcloud cr image-tag us.icr.io/birds/bluebird:peck us.icr.io/animals/dog:bark







 ibmcloud cr image-untag 

Remove a [tag](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_overviewoverview_elements_tag), or tags, from each specified image in IBM Cloud Container Registry.

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...]
If you want more control over the build of your image, then you can choose to [build the image](https://cloud.ibm.com/docs/codeengine?topic=codeengine-build-image) with Code Engine before you create and deploy your app.
* If you are starting with source code that resides on a local workstation, you can choose to let Code Engine take care of building the image from your source and deploying the app with a single CLI command. In this scenario, Code Engine uploads your image to IBM Cloud® Container Registry. To learn more, see [Deploying your app from local source code with the CLI](https://cloud.ibm.com/docs/codeengine?topic=codeengine-app-local-source-code) If you want more control over the build of your image, then you can choose to [build the image](https://cloud.ibm.com/docs/codeengine?topic=codeengine-build-image) with Code Engine before you create and deploy your app.



After your app is deployed, you can also [update your deployed app](https://cloud.ibm.com/docs/codeengine?topic=codeengine-update-app) by using any of the preceding ways, independent of how you created or previously updated your app.

When you deploy your application, 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.

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.
In the editor, search for the ranker-rest image (for example: {docker-registry}/{namespace}/discovery-ranker-rest-service:20200113-150050-2-d1527c2)
3. Add the following command below {docker-registry}/{namespace}/discovery-ranker-rest-service:20200113-150050-2-d1527c2:

command: "/tini"]
args: "-s", "-v", "--", "java", "-Dkaryon.ssl=true", "-Dkaryon.port=9081", "-Dkaryon.ssl.port=9090", "-Dkaryon.ssl.certificate=/opt/bluegoat/karyon/ssl/karyon-cert.pem", "-Dkaryon.ssl.privatekey=/opt/bluegoat/karyon/ssl/karyon-private-key.pem", "-Djavax.net.ssl.trustStore=/opt/bluegoat/karyon/ssl/keystore.jks", "-Djavax.net.ssl.keyStore=/opt/bluegoat/karyon/ssl/keystore.jks", "-Dlog4j.debug=false", "-Dlitelinks.threadcontexts=log4j_mdc", "-Dwatson.ssl.truststore.path=/opt/bluegoat/karyon/ssl/litelinks-truststore.jks", "-Dwatson.ssl.truststore.password=watson15qa", "-Dlitelinks.delay_client_close=false", "-Drxnetty.http.maxcontentlength=314572800", "-cp", "lib/logback-classic-1.2.3.jar::lib/", "com.ibm.watson.raas.rest.Runner"]!! ! ! ! !
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 API](https://cloud.ibm.com/docs/vpc?topic=vpc-image-from-volume-vpc-manageschedule-ilm-reset-status-change-API). After you remove the scheduled status change, you can make an immediate status change.



* Change image lifecycle status to deprecated.

curl -X POST "$vpc_api_endpoint/v1/images/$image_id/deprecate?version=2023-02-21&generation=2" -H “Authorization: Bearer $iam_token”
* Change the image lifecycle status to obsolete.

curl -X POST "$vpc_api_endpoint/v1/images/$image_id/obsolete?version=2023-12-21&generation=2" -H “Authorization: Bearer $iam_token”



To schedule a status change, use one of the following examples.

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.
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 deprecate-at and obsolete-at dates, the obsolete-at date must be after the deprecate-at date.

ibmcloud is image-update IMAGE [--deprecate-at YYYY-MM-DDThh:mm:ss+hh:mm] [--obsolete-at YYYY-MM-DDThh:mm:ss+hh:mm]

If you want to change the deprecate-at and obsolete-at date and time entries, you can run these commands again. The previous dates and times are then replaced with the new dates and times.





 Remove a previously scheduled custom image lifecycle status change by using the CLI 

You can remove a scheduled status change by using the --reset-deprecate-at or --reset-obsolete-at options. If you use either of these options with the ibmcloud is image-update command, the date and time are removed from the image. The image is no longer scheduled for that status change.

ibmcloud is image-update IMAGE [--reset-deprecate-at] [--reset-obsolete-at]

If you use both the --reset-deprecate-at and --reset-obsolete-at options, the image status returns to available.





 Change the custom image lifecycle status by using the API 

You can change the lifecycle status of an IBM Cloud VPC custom image by using the application programming interface (API). You can make an immediate status change or schedule a status change to happen later.

To make an immediate status change, use one of the following examples. For the$image_id variable, specify the ID of the custom image for the status change.
You cannot interrupt the automated management of frequency and you cannot trigger a one-off crawl when these types of scheduled crawls are configured.





If you want to change the flexible crawl schedule settings later, you can go to the Processing settings page, edit the settings, and then click Apply changes and reprocess.

IBM Cloud

The next scheduled crawl is displayed on the Activity page.

If you change the schedule frequency, the next scheduled crawl time might not be what you expect. The crawls are set up to occur on a regular schedule at a specific time or day by default. For example, if you change the crawl schedule from weekly to monthly on 11 August, the next crawl might be scheduled for 31 August instead of 11 September. It is not scheduled for exactly a month from the day that you made the change. Instead, it is scheduled to run on the day that is designated as the default run day for the selected crawl frequency.





 Stopping a crawl 

To stop a crawl, complete the following steps:



1. Open the Manage collections page from the navigation panel.
2. From the Activity page, if the crawl is not in progress, click Recrawl to start the crawl, and then click Stop.

IBM Cloud

After you stop a crawl, the crawl will not start again until you click Recrawl to restart it. When restarted, data from the data source is ingested from scratch, overwriting existing documents and adding new ones.