Troubleshooting issues when mirroring images for an air-gapped cluster
Troubleshoot errors you may get when mirroring images.
In the final procedure for mirroring images, the command fails with an error
Symptom: In the final procedure, "Mirror images to final location and configure the cluster", the command fails with this error:
error: unable to upload blob sha256:** no basic auth credentials
Cause: The registry credentials that you provided are incorrect.
Solution: In section 3.2, step 1, confirm that the value of
<TARGET_REGISTRY> includes the hostname and port for your registry server, and ensure that the username and password used for docker or podman login are correct.
Server misbehaving error when pulling an image
Symptom: You receive an error when pulling an image:
On one of the nodes, confirm that
/host/etc/containers/registries.confcontains all the rules defined in
ImageContentSourcePolicy(search for that string in the OpenShift web console). If
/host/etc/containers/registries.confdoes not contain those rules, copy them into the file.
Confirm that a
pullSecrethas been created in the
openshift-confignamespace. This is a global pull secret and contains a docker/podman login credential for the applicable registries, which gets copied onto the nodes. Credentials can be found in
<user_path>/kubelet/config.json. If the
pullSecretdoes not exist, you may need to contact IBM Support.
On the same node, confirm that the mirroring and the credentials are working. Pull the image manually with docker or podman, using the credentials from the preceding
config.jsonfile . For example:
docker pull <image-name>