-
Notifications
You must be signed in to change notification settings - Fork 138
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
image-check issue for internal registry #63
Comments
have you checked that the roxctl pod step have the proper permissions to access to the internal registry? Which version of OCP are you using? and the version of ACS is installed? |
Hi, This is a 4.10.59 OCP with v3.74.3 ACS. |
Sorry to inform the problem still exists in image-scan and image-check after creating the docker registry integration.. 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 |
Lemme try to reproduce it in a 4.10 env and I'll let you know. Thanks for opening the request! |
Hi,
Getting this in image-check task on OCP 4.10 during pipelinerun.
oc -n cicd logs petclinic-build-dev-75x4fy-image-check-pod -c step-rox-image-check
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 65.2M 100 65.2M 0 0 247M 0 --:--:-- --:--:-- --:--:-- 247M
Getting roxctl
ERROR: Checking image failed: could not check build-time alerts: rpc error: code = Internal desc = image enrichment error: error getting metadata for image: image-registry.openshift-image-registry.svc:5000/cicd/spring-petclinic@sha256:4b6e957cb83f6e5687b71c012343308fb15ac0bce23c1be85d9e2a29d340b29c error: getting metadata from registry: "Autogenerated https://image-registry.openshift-image-registry.svc:5000 for cluster development": Failed to get the manifest digest : Head "https://image-registry.openshift-image-registry.svc:5000/v2/cicd/spring-petclinic/manifests/sha256:4b6e957cb83f6e5687b71c012343308fb15ac0bce23c1be85d9e2a29d340b29c": http: non-successful response (status=401 body=""). Retrying after 3 seconds...
I found this: https://access.redhat.com/solutions/6993372
So wondering how this is working on your side..
Thanks
The text was updated successfully, but these errors were encountered: