Closed DimuthuSig closed 4 days ago
Thanks for reaching out — glibc
is at the OS layer and so it would need to be provided by whichever distribution you're using. For amazonlinux please consider opening an issue here: https://github.com/amazonlinux. On our end we do have an open feature request for moving to the CLI Docker image to AL2023: https://github.com/aws/aws-cli/issues/8331.
The default glibc
version on AL2023 is 2.34 per https://docs.aws.amazon.com/linux/al2023/ug/glibc-gcc-and-binutils.html. For issues with configure-aws-credentials please consider opening an issue in: https://github.com/aws-actions/configure-aws-credentials/ and share a full workflow file to reproduce the issue.
This issue is now closed. Comments on closed issues are hard for our team to see. If you need more assistance, please open a new issue that references this one.
Describe the bug
The action aws-actions/configure-aws-credentials@v4 fails with the error
/__e/node20/bin/node: /lib64/libm.so.6: version `GLIBC_2.27' not found (required by /__e/node20/bin/node) /__e/node20/bin/node: /lib64/libc.so.6: version `GLIBC_2.28' not found (required by /__e/node20/bin/node)
Expected Behavior
Authenticate with assumed role.
Current Behavior
Action fails immediately when running within the amazon/aws-cli:latest container.
Reproduction Steps
Add a Github actions run similar to the following
Possible Solution
nvm version
Additional Information/Context
No response
CLI version used
2.17.7
Environment details (OS name and version, etc.)
amazon-eks-node-1.28-v20240605