I tried to build the Docker image, but the build image fails.
If build image fails during installer tar file extraction or before the Docker build image starts, verify that adequate disk space is available in the current working directory.
PowerCenter requires 50 GB disk space in the current working directory.
If the build image fails at the step
in the log file, then there is not enough disk space in the Docker configuration directory. To find the Docker configuration directory, run the
PowerCenter requires 27 GB disk space in the Docker configuration directory.
You can also free up some space from the Docker configuration directory when you delete a dangling image. When you create the new build of the image but do not specify a new name, you create a dangling image and the old image becomes the dangling image. Those old images remain untagged and display "<none>" as the name when you run the
To delete the dangling images, complete the following steps:
To list all dangling images and to get the image ID, run the command:
docker images -f dangling=true
To delete each dangling image, run the command:
docker image rm -f <image id>
If the build image fails with the following error, you need to manually pull the Docker image:
Sending build context to Docker daemon 25.75GB
Step 1/30: FROM registry.access.redhat.com/rhel7:7.7
Trying to pull repository registry.access.redhat.com/rhel7 ...
To fix the issue, you can manually run the following command:
docker pull registry.access.redhat.com/rhel7:7.7
If the build image fails with the following error, the Docker build script has failed to access the repository to download dependencies:
This system is not registered with an entitlement server.
To register and subscribe the machine where you build the Docker image:
yum repolist all
command to see all the repositories.
to register with the following command:
subscription-manager repos --enable
To enable custom repositories, run the command:
If the build image displays the
error when you run the docker pull command to pull the image from RHEL, the authentication with the Docker authentication might have expired. Run the
command and then pull the Docker image. If the issue persists, try to pull the Docker image from registry.redhat.io instead of registry.access.redhat.com. If any issue remains with RHEL, you could try to use Centos7 for proof of concept cases.
I cannot access Administrator tool from the browser.
Check the IP address from where you access the Administrator tool:
For on-premises, verify that you specify the internal IP of the node on which the pod is running to access the Administrator tool.
For AWS or Azure, verify that you specify the external IP of the node on which the pod is running to access the Administrator tool.
For Azure, you will not have the external IP of the services by default. The service type of pod must be LoadBalancer instead of NodePort. It is from the LoadBalancer service type that you fetch the external IP.
If you want to verify that the external IP in the Administrator tool for Azure and AWS, run
kubectl get nodes -o wide
command followed by the
kubectl get svc -o wide
How do I restart an already running pod when it goes down?
When you have a pod that uses the persistent volume, a .yaml file gets generated under the image name folder inside the appconnTemp folder of the user home directory . Run the yaml file manually with the following command to restart the pod with persistent volume:
kubectl create -f <file name>.yaml
How do I to connect to different sources in pods?
In case of multiple DSN, you can manually update the ODBC.ini file.