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

Post authenticate to gcloud tokenzied - Github Actions #461

Closed
sravula84 opened this issue Jan 23, 2025 · 7 comments
Closed

Post authenticate to gcloud tokenzied - Github Actions #461

sravula84 opened this issue Jan 23, 2025 · 7 comments
Labels
bug Something isn't working

Comments

@sravula84
Copy link

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

- id: auth_google
        name: Authenticate to Google Cloud tokenized
        uses: google-github-actions/auth@v2
        with:
          token_format: "access_token"
          credentials_json: '${{ secrets.CICD_GCP_SERVICE_ACCOUNT_KEY }}'
          service_account: '${{ vars.CICD_GCP_SERVICE_ACCOUNT_NAME }}'
     - name: Build Docker Image with kaniko executor
        id: build_image
        run: |
       
          /kaniko/executor -f `pwd`/Dockerfile -c `pwd` --build-arg version=${CICD_ARTIFACT_VERSION} \
            --build-arg artifactory_publish_flag=${artifactory_publish_flag} \
            --build-arg schema_validate_flag=${cicd_schema_pr_validate} \
            --build-arg schema_file=${CICD_SCHEMA_FILE} \
            --build-arg apollo_key=${apollo_key} \
            --build-arg graph_name=${graph_name} \
            --build-arg service_name=${CICD_SERVICE_NAME} \
            --build-arg graph_env=${graph_env} \
            --build-arg artifactory_user=${ARTIFACTORY_USERNAME} \
            --build-arg artifactory_password=${ARTIFACTORY_PASSWORD} \
            --build-arg GITHUB_TOKEN=${{secrets.PROSPER_SRE_PAT}} \
            --build-arg GCP_TOKEN=${{ steps.auth_google.outputs.access_token }} \
            --destination=${CICD_ARTIFACT_FULL_NAME}:${CICD_ARTIFACT_VERSION} ${neuvector_tag_parameter}
                              
          echo "version=${CICD_ARTIFACT_VERSION}" >> "$GITHUB_OUTPUT"

Log output


Additional information

No response

@sravula84 sravula84 added the bug Something isn't working label Jan 23, 2025
Copy link

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.

@sravula84
Copy link
Author

i tried cleanup credentials flag = false but not working

@sethvargo
Copy link
Member

Are you using GitHub Actions self-hosted runners?

@sravula84
Copy link
Author

@sethvargo yes we are using self hosted runner scale sets, any suggestions

@sethvargo
Copy link
Member

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.

@sravula84
Copy link
Author

sravula84 commented Jan 29, 2025

i just verified ghcr.io/actions/actions-runner:latest image, i dont think node configured in this image
or am i checking the wrong one ?

@sethvargo
Copy link
Member

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 exec /__e/node16/bin/node: no such file or directory indicates that Node.js is missing. I found this issue on ARC which seems to be similar. This seems to be an issue with the self-hosted runner configuration, and not this specific GitHub Action.

@sethvargo sethvargo closed this as not planned Won't fix, can't repro, duplicate, stale Jan 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Development

No branches or pull requests

2 participants