-
-
Notifications
You must be signed in to change notification settings - Fork 170
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
oci_pull fails to pull a public gcr.io image without auth credentials #292
Comments
I believe that #284 is related as well when you have no auth credential helper |
@thesayyn has there been any update on this issue? thank you |
I've updated to the latest release of rules_oci (v1.3.4) and still having issues. It seems that rules_oci will fallback to using curl and that returns a different sha.
See a build failure here: https://buildkite.com/prysmatic-labs/prysm/builds/76220#018aa92a-25cd-4c5c-bfb1-df605799312f/35-90 |
Sounds like Curl doesn't properly fail... |
Another thing I noticed is that oci_pull does not work well with When removing that flag, CI is working again, albeit possibly slower to fetch dependencies. |
We have removed the Curl fallback now, i am not sure what needs to be done here. Does docker pull work fine with the same docker config? |
@thesayyn we have been running for two weeks with the experimental remote downloader flag and I haven't seen any issues. We are using rules_oci v1.7.4 without issues. Thanks for following up! |
Testing from commit ecbce02
The following function may fail with an error and stop the pull process when auth was never required.
rules_oci/oci/private/pull.bzl
Lines 149 to 160 in ecbce02
Example error:
If I disable the auth entirely with this patch, the pull works without issue. Obviously, this is not a fix but a proof of concept that auth is not required for every oci_pull.
A simple reproduction using gcp cloud shell
The text was updated successfully, but these errors were encountered: