vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Why is pulling images slow? 

Pulling an image is slow from IBM Cloud® Container Registry.

  What’s happening 

When you try to pull an image, it takes a long time.

  Why it’s happening 

The following alternatives are possible causes:



*  You are using a large image.
*  You are pulling your image over a long distance.
*  You have a poor connection.



  How to fix it 

You can fix this problem in the following ways:



*  Make your image smaller.
*  Store and pull your images in the same location.
*  If you're using IBM Cloud Kubernetes Service or Red Hat® OpenShift® Container Platform, you can pull images over the private network to get a faster speed.
Securing your data in Code Engine 

Code Engine provides a platform to unify the deployment of all your container-based applications. Whether those applications are functions, traditional 12-factor apps, batch workloads or any other container-based workloads, if they can be bundled into a container image, then Code Engine can host and manage them for you - all on a Kubernetes-based infrastructure. And Code Engine does this without the need for you to learn, or even know about, Kubernetes. As Code Engine is not a data service, it does not store personal or sensitive data.



 How your data is stored and encrypted in Code Engine 

While Code Engine does not store personal or sensitive data, when running Code Engine, the data that is stored by Code Engine includes references to container images where you run the images as Code Engine applications or batch jobs. Code Engine does not store the container image data. Instead, it uses the pointer that you provide to where your container image repository is located, which might be a public repository like Docker Hub or a private IBM Container Registry. Therefore, encryption of your data in your container images is implemented and managed as part of your container image repository.

Some data, like Docker Hub credentials, batch job templates and IBM container registry API key are stored as part of your namespace in Code Engine, within an underlying Kubernetes secret map (within your Kubernetes etcd data). For more information, see [Securing information in Kubernetes](https://cloud.ibm.com/docs/containers?topic=containers-encryption).





 Deleting your data in Code Engine 

Data in images is deleted within your container image repository.

To delete data that is stored within Code Engine, such as Docker Hub credentials, batch job templates, or an IBM container registry API key, [delete your Code Engine project](https://cloud.ibm.com/docs/codeengine?topic=codeengine-manage-projectdelete-project).

When you delete a project from the console or with the CLI, it is soft deleted and can be restored. You must restore your project within 7 days or it is permanently deleted.
When either the boot or load from image process is used, make sure that you back up all data that you might want to recover.



* Boot from image starts a device by using an ISO supplied by IBM Cloud® for system recovery or an ISO that was uploaded by using the Import image feature in the IBM Cloud console. The ISO might be a clean version of the device operating system or a recovery disk that is used in an attempt to remedy an issue with the device.
* Load from image is a method of OS reload that uses an image template that was either captured from a device or uploaded by using the Image import feature in the IBM Cloud console. Load from image uses a VHD that wipes the device of all data and replaces the existing operating system and files with a "like new" version of the selected image.







 I lost my password to my server. How can I recover it? 

If the root or administrator password to your server is suddenly not working, check the following items. If necessary, use the instructions to start rescue mode and reset your password.



* Are you copying and pasting the password? If not, try to. Also, paste the password in a notepad to make sure that no spaces are accidentally being copied with the password.
* If the server has cPanel, it's possible that cPHulk blocked your IP address due to failed logins. You can access the server by using the KVM or IPMI and allowlist your IP address. Use cPHulk with "/scripts/cphulkdwhitelist" followed by your IP address.
* Has someone recently tried to change the password for the server by modifying the password in the IBM Cloud console? Changing the password in the IBM Cloud console changes what you see as the password. It doesn't change the server password. If so, you can contact [Support](https://cloud.ibm.com/docs/get-support?topic=get-support-using-avatar) and they can usually recover the original, working password.
* You might need to start into rescue mode to reset your password.
The Cache-Control HTTP response header provides a suggestion for the client cache mechanisms on how to treat the returned information. IBM Cloudant typically returns the must-revalidate value, which indicates that the information must be revalidated if possible. Revalidation ensures that the dynamic nature of the content is correctly updated.





 Content-Length 

The Content-Length header reports the length in bytes of the returned content.





 Content-Type for response headers 

The Content-Type header specifies the MIME type of the returned data. For most request, the returned MIME type is text/plain. All text is encoded in Unicode (UTF-8), which is explicitly stated in the returned Content-Type as text/plain;charset=utf-8.





 Etag 

The Etag header is used to show the revision for a document. For documents, the value is identical to the revision of the document. The value can be used with an If-None-Match request header to get a [304 Not Modified](https://cloud.ibm.com/apidocs/cloudantlist-of-http-codes) response if the revision is still current.

ETags cannot currently be used with views, since the ETags returned from those requests are random numbers that change on every request.







Contribute in GitHub

Open doc issue

Edit topic





On this page[HTTP headers](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-how-http-works-with-cloudanthttp-headers)[Request headers](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-how-http-works-with-cloudantrequest-headers)[Response headers](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-how-http-works-with-cloudantresponse-headers)


Feedback

Focus sentinel

 Give us your feedback 

Tell us about your experience0/1500



Don't include any sensitive or personal information.

How satisfied are you with your experience?

How satisfied are you with your experience?

1

2

3

4
Planning your build 

Before you start building images with IBM Cloud® Code Engine, learn about the different options you have for your build.

A build, or image build, is a mechanism that you can use to create a container image from your source code. Code Engine supports building from a Dockerfile and Cloud Native Buildpacks.

If you have an image build that exists in a container registry and the image was built with a non-Intel based processor, Code Engine cannot run your container image. Code Engine uses Intel-based processing. You can build your own image if you use Intel processing (x86 processor). You can also choose to let Code Engine handle the build process for you.

Code Engine provides custom resource definition (CRD) methods. For more information, see [Code Engine API reference - Source-to-image CRD methods](https://cloud.ibm.com/docs/codeengine?topic=codeengine-apiapi-crd-s2i).



 Prepare your source location 

To give Code Engine access to your source code, you need to make it available in a Git repository or in an accessible location on your local workstation.

Git repository
: Store your code in a Git repository, for example in [GitHub](https://github.com/) or [GitLab](https://gitlab.com). Your code can be at the top level of your repository or in a subdirectory. If your source repository is not public, you must add [access to Code Engine](https://cloud.ibm.com/docs/codeengine?topic=codeengine-code-repositories).

Local workstation
: Store your code on your local workstation. When you submit a build that pulls code from a local directory, your source code is packed into an archive file and uploaded to your IBM Cloud Container Registry instance. The source image is created in the same namespace as your build image. Note that you can target only IBM Cloud Container Registry for your local builds.
Feedback/clicks 

If you are storing clicks in the form of feedback events, there is currently no easy way to back up and restore this information. The recommendation is to start from scratch with the [clicks/feedback data](https://cloud.ibm.com/apidocs/discoverycreate-event) API.





 Expansion lists 

If you are using expansions for query modification, back up your expansion list, and store it locally. To do so, request the expansion list ,using the [get expansion list](https://cloud.ibm.com/apidocs/discoveryget-the-expansion-list) API command, and store it locally.





 Tokenization dictionaries or stopwords 

If you use these capabilities, back up these files, and store them locally. In the case of stopwords, back up the text file, and in the case of the tokenizations, back up the JSON file. For more information about each file type, see [Creating custom tokenization dictionaries](https://cloud.ibm.com/docs/discovery?topic=discovery-query-conceptstokenization) and [Defining stopwords](https://cloud.ibm.com/docs/discovery?topic=discovery-query-conceptsstopwords).





 Collection information 

This is not required, but it is a good best practice to [retrieve the status](https://cloud.ibm.com/apidocs/discoveryget-collection-details) for each collection on a regular basis and store the information locally. By retaining these statistics, you can later verify that your restoration processes were successful if needed.





 Smart Document Understanding models 

If you use Smart Document Understanding (SDU), you have models associated with your configuration. To avoid loss of this information, [export your models](https://cloud.ibm.com/docs/discovery?topic=discovery-sduimport), back them up, and store them locally. SDU models have the file extension of .sdumodel.







 Restoring your data to a new Watson Discovery instance 

Consider using your backups to restore to a new Discovery instance in a different Data Center, also known as a region or location.
(https://cloud.ibm.com/docs-content/v1/content/f16b1f78a92498247223b337bd9303c2758b9ba8/discovery-data/images/tut-sdu-tool.png)

Figure 12. PDF is displayed in the SDU tool

The tool shows you a view of the original document along with a representation of the document, where the text is replaced by blocks. The blocks represent field types.

Initially, the blocks are all the color of the text field label because all of the document content is considered to be standard text and will be indexed in the text field.

A Field labels list shows the predefined field labels that are available.

We are going to label blocks that represent specific types of information, such as titles and subtitles, with corresponding field labels. (The process of using labels to identify different parts of the document's structure is called annotating the document.)
5. To annotate the document, click the label first. Then, click the block of text that you want to label.

Click title from the Field labels list, and then, in the document representation, click the yellow block that is situated in the location of the document title.

Zoom

![Shows the title that is being labeled in the SDU tool.](https://cloud.ibm.com/docs-content/v1/content/f16b1f78a92498247223b337bd9303c2758b9ba8/discovery-data/images/tut-sdu-label-title.png)

Figure 13. A title is being labeled in the Smart Document Understanding tool

You labeled the title of the document successfully!
6. The rest of the text on the page can be indexed as part of the text field. Therefore, click Submit page.
7. The next page is the Table of contents for the document. Click the table_of_contents label, and then select all of the text on the page to label it.
If you need to find document conflicts, use the following example map function:

function (doc) {
if (doc._conflicts) {
emit(null, [doc._rev].concat(doc._conflicts));
}
}

If you want to find conflicts within multiple documents in a database, write a [view](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-creating-views-mapreduce).
* What happens if I ignore conflicts?

If you don't check for conflicts, or don't fix them, your IBM Cloudant database has the following problems:



* Document inconsistency increases because conflicting documents continue to multiply.
* Database size increases because documents with conflicts must be kept until the conflict is resolved.
* Performance degrades because it takes more work for IBM Cloudant to respond to each request since it has to go through all the conflicted documents to find the "best possible" version.



* How do I resolve conflicts?

After you find a conflict, follow these four steps to resolve it.



1. [Get](https://cloud.ibm.com/docs/services/Cloudant?topic=Cloudant-document-versioning-and-mvccget-conflicting-revisions-mvcc) the conflicting revisions.
2. [Merge](https://cloud.ibm.com/docs/services/Cloudant?topic=Cloudant-document-versioning-and-mvccmerge-the-changes-mvcc) them into your application or ask the owner what to do.
3. [Upload](https://cloud.ibm.com/docs/services/Cloudant?topic=Cloudant-document-versioning-and-mvccupload-the-new-revision-mvcc) the new revision.
4. [Delete](https://cloud.ibm.com/docs/services/Cloudant?topic=Cloudant-document-versioning-and-mvccdelete-old-revisions-mvcc) old revisions.



* Migration FAQ

 Migration FAQ
It is helpful to leave the feature on if your replication is to resume efficiently from its last known position.





 Permissions 

Admin access is necessary to insert a document into the _replicator database. The login credentials that are supplied in the source and target parameters do not require full admin permissions. It is sufficient if the credentials perform the following tasks:



* Write documents at the destination end.
* Write checkpoint documents at both ends.



IBM Cloudant has a special _replicator user permission. This permission allows checkpoint documents to be created, but does not allow the creation of ordinary documents in a database. In general, [create API keys](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-work-with-your-accountcreating-api-keys) that have:



* _reader and _replicator access at the source side.
* _reader and _writer access at the destination side.



API keys can be created and configured within the IBM Cloudant Dashboard, on a per-database basis.

Zoom

![API keys can be created and configured within the IBM Cloudant Dashboard, on a per-database basis.](https://cloud.ibm.com/docs-content/v1/content/522c6f62358b063f921283400a601c3f9bc66f08/Cloudant/images/replication_guide_5.png)

Figure 4. IBM Cloudant users and API keys with permissions

They can also be created [programmatically](https://cloud.ibm.com/apidocs/cloudantintroduction) by using the IBM Cloudant API.

For security purposes, the IBM Cloudant team recommends that you use IAM API keys or IBM Cloudant legacy authentication [API keys](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-work-with-your-accountapi-keys) rather than account-level credentials for replication jobs.
Create a time series per location, set the time series TRS with default start time and 1 ms granularity, and store with it with the name "ts".

SELECT
location,
ts
FROM cos://us-geo/sql/temperature_humidity.csv
USING TIME_SERIES_FORMAT(key="location", timetick="timestamp", value="humidity", granularity="PT0.001S") in ts

Create a time series per location, set the time series TRS with start time "2011-12-03T10:15:30" and default granularity (1 ms), and store it with the name "ts".

SELECT
location,
ts
FROM cos://us-geo/sql/temperature_humidity.csv
USING TIME_SERIES_FORMAT(key="location", timetick="timestamp", value="humidity", starttime="2011-12-03T10:15:30") in ts

Create a time series per location with no TRS, store it with the name "ts". If no granularity or start time is provided, a TRS is not associated with the time series, and therefore with_trs runs into exception.

SELECT
location,
ts
FROM cos://us-geo/sql/temperature_humidity.csv
USING TIME_SERIES_FORMAT(key="location", timetick="timestamp", value="humidity") in ts

Create a single time series, store it with the default name "time_series". Without specifying a key, it is not possible to create multiple time series.

SELECT
location,
time_series
FROM cos://us-geo/sql/temperature_humidity.csv
USING TIME_SERIES_FORMAT(timetick="timestamp", value="humidity")





 tableTransformer 

A table transformer is a function that is applied to the input data set before it is sent to the actual SQL query compilation and execution.

You can wrap your external table definition optionally with the FLATTEN table transformation function.
This database is in the same IBM Cloudant instance or in another IBM Cloudant instance on the other side of the world. IBM Cloudant also replicates to and from Apache CouchDB and PouchDB databases on the public internet.





 What happens after HTTP support is removed? 

Following this change, a replication that is configured with the http:// protocol fails permanently. The replication job is not retried. Any replications using the https:// protocol are unaffected.





 How do I know whether my replications use HTTP? 

Replication job definitions are stored in documents in an IBM Cloudant account's _replicator database, for example:

{
"_id": "myreplicationjob",
"source": "https://mycloudantservice.cloudant.com/products",
"target": "http://myselfhostedcouchdb.mydomain.com/products"
}

If either the source or target URLs contain an http:// prefix, then the replication job is affected and action must be taken to ensure the replication runs.





 How do I avoid being affected? 

If a self-hosted CouchDB service supports HTTPS, then change the replication definition to contain an https:// prefix, as shown in the following example:

{
"_id": "myreplicationjob",
"source": "https://mycloudantservice.cloudant.com/products",
"target": "https://myselfhostedcouchdb.mydomain.com/products"
}

IBM Cloudant restarts the replication from where the old replication job stopped.

If a self-hosted CouchDB service does _not* support HTTPS, CouchDB can mediate replication jobs instead of IBM Cloudant. For example, stop the replication job that runs on the IBM Cloudant side and set up a replication job on a self-hosted Apache CouchDB service to "pull" the data from IBM Cloudant.

IBM Cloudant supports only https:// traffic, so if IBM Cloudant is to be the source or target in a self-hosted replication definition, it must be configured with an https:// prefix.
* [Enable the root key for the IBM® Key Protect for IBM Cloud® instance](https://cloud.ibm.com/docs/key-protect?topic=key-protect-disable-keysenable-root-key) that is associated with your Continuous Delivery service, in the region where you want to view the toolchain.
* [Enable the root key for the IBM Cloud® Hyper Protect Crypto Services instance](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-disable-keysenable-ui) that is associated with your Continuous Delivery service, in the region where you want to view the toolchain.







 When I use Terraform or the API to configure a tool integration, why does the configuration fail with the Could not find value for secret reference... error? 

The tool integration is configured with a reference to a secret, but the toolchain cannot find the referenced secret or secret store.

 What’s happening 

When you use Terraform or the API to create or update a tool integration, the configuration fails with the Could not find value for secret reference... error message.

 Why it’s happening 

Many tool integrations include configuration properties that are classified as secrets. When you set these properties in a Terraform resource or API call, you can set them as [secrets references](https://cloud.ibm.com/docs/ContinuousDelivery?topic=ContinuousDelivery-cd_data_securitycd_secrets_references). A secret reference is a specially formatted string that identifies the name and location of a secret in a secret store that is integrated into the toolchain. This error indicates that the toolchain cannot find the identified secret, or that the secret store is not integrated into the toolchain. The error can occur for secrets references by name if one or more of the segments in the secrets reference {vault:...} string are incorrect, or if a key of the specified group, name, or field does not exist in the secret store. The error can occur for secrets references by CRN if the secret CRN references a secret that was deleted.

 How to fix it
* [vCenter Virtual Appliance]]([https://my.vmware.com/web/vmware/info/slug/datacenter_cloud_infrastructure/vmware_vsphere/5_5](https://my.vmware.com/web/vmware/info/slug/datacenter_cloud_infrastructure/vmware_vsphere/5_5)){: external} (requires a valid VMware subscription)



After you download the ISO, you need to upload the image to a management host data store so it can be attached to a virtual machine. Use the vSphere client to connect to a management host and create an ISO directory on the local data store.





 Step 8 Deploying DNS 

You need to deploy a VM (on a management host) and install DNS services. Use the traditional vSphere client to create a VM on the Management ESXi host where the Windows or Linux ISO is located. Connect the appropriate ISO (Windows or CentOS) to deploy a DNS server on the VM. Make sure to associate the VM to the VM port group (vmpg)-management port group that was created in a previous step.

After the VM is installed, assign an IP address and default gateway from the portable private subnet group. If you are using the VLAN worksheet in Appendix A, the Management VM subnet. Update the Notes section of each Portable IP address with the name of the VM assigned. The Notes section can be located by going to the IBM Cloud infrastructure customer portal and selecting Network > IP Management > Subnets > [Subnet].

Although it is beyond the scope of this document to detail the steps that are needed to enable DNS, the following guidance is provided:



1. Set DNS Forwarding to the service.softlayer.com local DNS hosts:



* rs1.service.softlayer.com 10.0.80.11
* rs2.service.softlayer.com 10.0.80.12



2.