-
Notifications
You must be signed in to change notification settings - Fork 706
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
Staled content image: quay.io/complianceascode/ocp4:latest
#8495
Comments
quay.io/complianceascode/ocp4:latest
Thanks for filing the bug. Providing some additional context. I'm getting the following error when I run the tests locally:
Which causes the scans to fail even though the issue was fixed upstream [0]. [0] #8348 |
Hi, I'd like to understand the status of this issue because I need to use the latest |
We are planning to fix this and we're working on a solution to update the content. Hopefully we'll have something running this week. |
Hi, is there any update on this issue? Although I can personally use self-built image, customers using public CO instances such as installed via OperatorHub rely on this public image. |
We have new content available here https://quay.io/repository/compliance-operator/compliance-operator-content I'm in the process of updating references in compliance-operator and test repositories. openshift/compliance-operator#821 |
The CI against openshift/compliance-operator is running with the new content. @JAORMX has a patch to push additional content images to ghcr.io, too. |
Description of problem:
The
quay.io/complianceascode/ocp4:latest
image seems stale, the last update to it was from two months ago. We use this image as our compliance operator upstream image as well as in our CI.The text was updated successfully, but these errors were encountered: