-
Notifications
You must be signed in to change notification settings - Fork 211
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
Post authenticate to gcloud tokenzied - Github Actions #461
Comments
Hi there @sravula84 👋! Thank you for opening an issue. Our team will triage this as soon as we can. Please take a moment to review the troubleshooting steps which lists common error messages and their resolution steps. |
i tried cleanup credentials flag = false but not working |
Are you using GitHub Actions self-hosted runners? |
@sethvargo yes we are using self hosted runner scale sets, any suggestions |
Based on the error message, it looks like the version of Node.js running on the self-hosted runners are EOL and no longer supported by GitHub or GitHub Actions. I recommend upgrading to at least Node.js v20. |
i just verified ghcr.io/actions/actions-runner:latest image, i dont think node configured in this image |
I'm not sure how your self-hosted runners are configured (there are many possible configurations), and we can't provide support for all those different configurations. The error message |
TL;DR
we are facing below issue some times, any suggestions ?
Post job cleanup.
/usr/bin/docker exec 853a38b4daf26272e86a9e5e1faec7a8fca2b5335c54a66d5abcae8f595c6263 sh -c "cat /etc/*release | grep ^ID"
exec /__e/node16/bin/node: no such file or directory
Expected behavior
post build step should clean gcloud credentials
Observed behavior
unable to delete the credentials
Action YAML
Log output
Additional information
No response
The text was updated successfully, but these errors were encountered: