Skip to content

Consider using docker-credential-gcr for authenticating to GAR #919

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

Closed
dsotirakis opened this issue Apr 23, 2025 · 0 comments · Fixed by #925
Closed

Consider using docker-credential-gcr for authenticating to GAR #919

dsotirakis opened this issue Apr 23, 2025 · 0 comments · Fixed by #925
Assignees

Comments

@dsotirakis
Copy link
Contributor

dsotirakis commented Apr 23, 2025

Source.
auth_token's expiration time is 5 minutes which makes things hard for pipelines that take longer than >5m to finish. What happens is that login-to-gar runs and authenticates successfully, then the next step takes more than 5 minutes to execute and by the time pipeline needs to push to GAR, the token expires and returns 401. This results in users being unable to use our actions.

As an alternative solution, we can use the docker-credential-gcr standalone helper, which can help with authenticating in GCP, for the GAR case (won't work with GCS).

This means, that we'll need to also persist the credentials file until the docker configuration step runs, but we can remove the credential files after the job is done.

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

Successfully merging a pull request may close this issue.

1 participant