Che install fails due to failed image pulls from registry.redhat.io
See original GitHub issueThe operator previously used images from http://registry.access.redhat.com/ which were accessible without login but was recently changed to use images from registry.redhat.io which requires registration and login.
This is the change in question: https://github.com/eclipse/che-operator/commit/bfd906590ecba054d5708f3b4bd0ea4fc849815c
Normal Scheduled 3m6s default-scheduler Successfully assigned che/mkdir-workspacemrx3pppo18kngsfu to 9.42.19.223
Normal Pulling 82s (x4 over 3m5s) kubelet, 9.42.19.223 pulling image "registry.redhat.io/ubi8-minimal:8.0-127"
Warning Failed 71s (x4 over 3m4s) kubelet, 9.42.19.223 Failed to pull image "registry.redhat.io/ubi8-minimal:8.0-127": rpc error: code = Unknown desc = Error response from daemon: Get https://registry.redhat.io/v2/ubi8-minimal/manifests/8.0-127: unauthorized: Please login to the Red Hat Registry using your Customer Portal credentials. Further instructions can be found here: https://access.redhat.com/articles/3399531
Warning Failed 71s (x4 over 3m4s) kubelet, 9.42.19.223 Error: ErrImagePull
Warning Failed 56s (x6 over 3m3s) kubelet, 9.42.19.223 Error: ImagePullBackOff
Normal BackOff 43s (x7 over 3m3s) kubelet, 9.42.19.223 Back-off pulling image "registry.redhat.io/ubi8-minimal:8.0-127"
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
RHOCP Failed to pull image from "registry.redhat.io"
Issue. Getting image pullback error for pod(s) when downloading image(s) from registry.redhat.io. Environment. Red Hat OpenShift Container ...
Read more >Red Hat Container Registry Authentication
Note: for pulling images from a Red Hat OpenShift Container Platform cluster, it's needed to check if the current pull secret is valid....
Read more >Workaround for manifest unknown failure to pull the ...
You can verify whether the image failed to pull is existing or not on the RH registry using "SHA256" Digest through "skopeo inspect"...
Read more >confusing/messy error message on build image pull failure
A failure to pull an image in a build(due to missing creds) results in an error ... failed due to error: while pulling...
Read more >Search OpenShift CI - OKD
#2106770 bug 5 months ago
#2101880 bug 4 months ago
#1997490 bug 15 months ago
#1904485 bug 2 years ago
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Suggested solution (in Eclipse Che MM channel) is to have:
And to use this new
DefaultPvcJobsUpstreamImage
as the default in Che, whileDefaultPvcJobsImage
is the default for CRW.Not sure if this change should be applied to the 1.x branch, or reserved for the master (Che 7 / CRW 2) branch. Leaning toward master only as it doesn’t change behaviour in the Che 6.x / CRW 1.x branch. Or is this a blocker for Che 6.x users too?
3 weeks later, might as well close.