IBM Informix Standalone Container v2.0.0 - Images not found in cp.icr.io/cp/
Ivelina Vardeva could not deploy IBM Informix Standalone Container v2.0.0 on OpenShift; pods failed with ErrImagePull and manifest unknown for informix-hq, -cm and -eng. Daniel Weber said the images live under icr.io/cpopen/informix/ and the charts were using a wrong path. He was investigating a workaround with an image mirror configuration. Unresolved.
Auto-generated by Claude from the posts below — may be imperfect; read the full thread.
Hello, I am trying to deploy IBM Informix Standalone Container v2.0.0 on Red Hat OpenShift using the CASE bundle from: https://github.com/IBM/cloud-pak/tree/master/repo/case/ibm-informix-standalone The operator deploys successfully, but pods fail with ErrImagePull for images like: icr.io/cp/informix-hq icr.io/cp/informix-cm icr.io/cp/informix-eng Error: manifest unknown on both icr.io/cp/ and cp.icr.io/cp/ I have a valid IBM Software Access entitlement key with "all" container software access. Could you please confirm: The exact image names and tags available in the registry? The correct registry URL for Informix Standalone Container v2.0.0? Thank you! ------------------------------ Ivelina Vardeva ------------------------------
Hello Ivelina, Can you do two things for me ? First, can you provide the image digests the pods are referencing when pulling the images? Second, if you delete a pod does it successfully pull the image ? Regards, Dan Weber ------------------------------ Daniel Weber ------------------------------
Hi, We are looking into this but need additional info. Please share the digest of one of the images from a pod in the image pull error state and what happens if you restart (delete) the pod ? Thanks! ------------------------------ Karen Qualley ------------------------------
The location of the images are as follows - icr.io/cpopen/informix/informix-hq:2.0.0-0000-x86_64 I'm looking into why the charts aren't using the case validated path for the deployment. ------------------------------ Daniel Weber ------------------------------
I believe I found where the invalid path is being interjected into the resource yaml files. Investing a workaround using an image mirror configuration. ------------------------------ Daniel Weber ------------------------------