Skip to content
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

403 on pushing image to GCR #161

Open
fermelone opened this issue Mar 15, 2020 · 1 comment
Open

403 on pushing image to GCR #161

fermelone opened this issue Mar 15, 2020 · 1 comment

Comments

@fermelone
Copy link

Followed the guide here exactly, and I'm getting a 403 when Jenkins tries to upload the image to GCR using the command: gcloud builds submit -t ${IMAGE_TAG} .

Getting: `ERROR: (gcloud.builds.submit) HTTPError 403: Insufficient Permission``

However, I added a few gcloud commands before that, such as:
gcloud container images list
and it works, so I figured that it had to be the permissions on storage or buckets, but checked this in IAM and it seems to be ok, I can authenticate manually with the service account used, and I can upload things manually to GCR.

So my final thought is that the problem resides in the way Jenkins inherits gcloud accounts to execute stage commands.

Does anything sound familiar here? like a known issue?
It's important to mention that the option Google service account from metadata does now work when adding new credentials in my Jenkins instance (also created with your guide). I had to upload a json key file to add credentials, and it seems to be working for all other commands, except the one I mentioned before, uploading images to GCR.

Thanks!

@Juanmanuelramirez
Copy link

did you solve it ?
I got a similar error
Failed to initialize HTTP transport: hudson.AbortException

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants