This does not seem helpful. For example every Lambda image (at the time of this writing ex: NodeJS v16) seems to have a version of glibc v2.2.6 released on 2017-08-02. We need a way to update glibc now? Answer from MetaSkills on repost.aws
Reddit
reddit.com › r/aws › how to upgrade glibc on amazon linux 2 ami
r/aws on Reddit: How to upgrade glibc on Amazon Linux 2 AMI
March 1, 2022 -
On EC2 instances using Amazon Linux 2, an outdated version of glibc is used: glibc 2.26. That is backed up by the FAQ for Amazon Linux 2. FAQ for Amazon Linux 2.
A set of core packages including systemd, GCC 7.3, Glibc 2.26, Binutils 2.29.1 that receive Long Term Support (LTS) from AWS.
Is there any way to upgrade to a newer version of Glibc, like 2.28? For background, I am trying to run a Python Docker image that is using glibc 2.28 and is running into conflicts since the 2.26 version is being used in the instance.
AWS
docs.aws.amazon.com › amazon linux › user guide › what is amazon linux 2023? › core toolchain packages glibc, gcc, binutils
Core toolchain packages glibc, gcc, binutils - Amazon Linux 2023
May 22, 2026 - Learn about the purposes of new core toolchain packages that build most software in your distribution.
node.js - GLIBC_2.27 not found while installing Node on Amazon EC2 instance - Stack Overflow
If your package manager can't install a new-enough version of glibc, you need to be on a newer version of your operating system. In Ubuntu, you can accomplish an OS upgrade with do-release-upgrade. ... and because the question is about Amazon Linux, if you want to go from Node 16 to Node 18 ... More on stackoverflow.com
Amazon Linux 2 support dropped due to glibc >= 2.28 requirement
Is this a deliberate change or is there a chance you might be able to support a lower GLIBC version to allow Amazon Linux 2 users to continue to upgrade past 0.21.0 (what we're using). More on github.com
1
April 4, 2023Workaround for machines that do not have `glibc` >= 2.28
It will make all Amazon Linux 2 (AL2) EC2 machines unable to use VS Code, while also affecting enterprise users who may use customized or parallel versions of the glibc library for their own development needs. More on github.com
38
January 24, 2024Elastic-ci AMI based on Amazon linux 2 - GLIBC_2.27 missing
Hi Team, We ran into an issue today where we upgrade our node repositories to node 18 LTS, which requires GLIBC_2.27 but it seems Amazon linux 2 does not support GLIBC_2.27. We are currently using the AMI ami-037cc66b7b94d90aa published on 25/07/2023. I see there is a new AMI available ... More on forum.buildkite.community
4
0
August 16, 2023 Top answer 1 of 4
2
This does not seem helpful. For example every Lambda image (at the time of this writing ex: NodeJS v16) seems to have a version of glibc v2.2.6 released on 2017-08-02. We need a way to update glibc now?
2 of 4
2
I've been trying to update GLIBC to 2.27, but kept failing. It says it's all up-to-date and GLIBC 2.26 is the latest verions.
I found this on AWS. Does this mean that I am allowed to use specific (2.26 version) GLIBC only and not allowed to update?
!Enter image description here
Also, I tried to launch an EC2 with **"Amazon Linux 2022"**, but I don't see an image for **AL 2022**.
AWS
docs.aws.amazon.com › amazon linux › user guide › comparing al2 and al2023 › improved toolchain: gcc, binutils, and glibc
Improved toolchain: gcc, binutils, and glibc - Amazon Linux 2023
AL2023 includes many of the same core packages as AL2.
Top answer 1 of 14
164
Try installing the active LTS version instead of latest with nvm install 16 (instead of nvm install node) as per the examples.
This was tested on the docker image amazonlinux:2 and correlates to what AWS CDK supports (ref)
Update
LTS has moved on for node, however, as per @djvg's comment, note there is a limitation with amazon linux 2 on glibc, so if requiring node > 16 will need to move to newer amazon linux version, eg: https://github.com/amazonlinux/amazon-linux-2023/blob/main/Release-Notes-Amazon-Linux-2022.0.20220728.0.md
2 of 14
49
It seems like you are using v.18.0.0 which was the latest but not well-supported.
Try uninstalling that.
nvm uninstall 18.0.0
Install a version that is active.
nvm install 16.0.0
You should now be using v16 which should be well-supported.
LinuxQuestions.org
linuxquestions.org › questions › linux-newbie-8 › glibc-update-to-2-27-in-amazon-linux-4175633861
glibc update to 2.27 in amazon linux
I am trying to update glibc package update in amazon linux AMI, could some please help me how to update the glibc this is regarding to CVE-2017-15804
Tenable
tenable.com › plugins › nessus › 171823
Amazon Linux 2 : glibc (ALAS-2023-1944)<!-- --> | Tenable®
February 17, 2023 - Run 'yum update glibc' to update your system. https://alas.aws.amazon.com/AL2/ALAS-2023-1944.html · https://alas.aws.amazon.com/cve/html/CVE-2019-19126.html · https://alas.aws.amazon.com/cve/html/CVE-2020-10029.html · https://alas.aws.amazon.com/cve/html/CVE-2020-1752.html ...
Installati.one
installati.one › home › amazonlinux › 2nd › how to install glibc.x86_64 on amazon linux 2
How To Install glibc.x86_64 on Amazon Linux 2 | Installati.one
May 20, 2022 - In this tutorial we learn how to install glibc.x86_64 on Amazon Linux 2. The glibc package contains standard libraries which are used by multiple programs on the system. In order to save disk space and memory, as well as to make upgrading easier, common system code is kept in one place and ...
AWS
docs.aws.amazon.com › amazon linux › user guide › al2 on amazon ec2 › configure al2 instances › manage software on your al2 instance › update instance software on your al2 instance
Update instance software on your AL2 instance - Amazon Linux 2
Update a single software package or all packages within an AL2 instance.
Top answer 1 of 4
1
You have duplicate packages, and maybe other corruptions too. Try these commands:
package-cleanup --cleandupes # Removes duplicate packages
rpm --rebuilddb # Rebuilds RPM database
yum reinstall glibc nss-softokn-freebl vim-filesystem
When that works, see if yum is happy:
yum check dependencies
If it's complaining about dependencies, install them first.
2 of 4
0
Please try
sudo yum clean all
sudo yum update
GitHub
github.com › osohq › oso › issues › 1694
Amazon Linux 2 support dropped due to glibc >= 2.28 requirement · Issue #1694 · osohq/oso
April 4, 2023 - Amazon Linux 2 has a maximum glibc version of 2.26. There's no intention to update this and instead Amazon are pushing Amazon Linux 2023 which recently went generally available. Recent Oso versions require glibc >= 2.28: LoadError: Could...
Author osohq
Pkgs
amazonlinux.pkgs.org › 2 › amazonlinux-core-x86_64 › glibc-devel-2.26-58.amzn2.x86_64.rpm.html
glibc-devel-2.26-58.amzn2.x86_64.rpm
We cannot provide a description for this page right now
GitHub
github.com › microsoft › vscode › issues › 203375
Workaround for machines that do not have `glibc` >= 2.28 · Issue #203375 · microsoft/vscode
January 24, 2024 - It will make all Amazon Linux 2 (AL2) EC2 machines unable to use VS Code, while also affecting enterprise users who may use customized or parallel versions of the glibc library for their own development needs.
Author microsoft
AWS
aws.amazon.com › blogs › developer › linux-support-updates-for-aws-cli-v2
Linux Support Updates for AWS CLI v2 | AWS Developer Tools Blog
August 6, 2025 - For users unable to upgrade, we recommend either remaining on their currently installed version of AWS CLI v2, or installing AWS CLI v2 version 2.17.49 or prior. For more information on installing past releases of the AWS CLI v2, please visit the installation docs. If you’re currently using AWS CLI v2 on a Linux distribution with glibc ...
Top answer 1 of 4
1
The upgrade to the latest template version worked.
We have upgraded from Buildkite stack v5.20.0 to Buildkite stack v6.3.0.
There were minor changes in the parameter key’s which gave us issues initially for the upgrade, but when identified, we updated our parameters and it upgrade was fine.
The l…
2 of 4
0
I just checked, the latest release of Buildkite elastic-ci is based on amazon linux 2023
[image]
Release v6.2.0 · buildkite/elastic-ci-stack-for-aws
v6.2.0 (2023-08-09)
Full Changelog
Changed
Change base image to Windows Server 2019 w/o containers and install Docker CE (v24.0.5) #1180 (…
Tenable
tenable.com › plugins › nessus › 146627
Amazon Linux 2 : glibc (ALAS-2021-1605)<!-- --> | Tenable®
February 19, 2021 - Run 'yum update glibc' to update your system. https://alas.aws.amazon.com/AL2/ALAS-2021-1605.html
Caddy Community
caddy.community › help
Install on Amazon Linux EC2 fails. 'Requires: libc.so.6(GLIBC_2.34)(64bit)' - Help - Caddy Community
December 9, 2022 - 1. Output of caddy version: N/A (can’t install it) 2. How I run Caddy: N/A (cannot install it) a. System environment: Amazon Linux, AWS EC2 AMI: amzn2-ami-kernel-5.10-hvm-2.0.20221103.3-x86_64-gp2 I have Docker set…
Tenable
tenable.com › plugins › nessus › 119468
Amazon Linux AMI : glibc (ALAS-2018-1109)<!-- --> | Tenable®
Run 'yum update glibc' to update your system. ... Supported Sensors: Frictionless Assessment AWS, Frictionless Assessment Agent, Nessus Agent, Agentless Assessment, Continuous Assessment, Nessus ... CPE: p-cpe:/a:amazon:linux:glibc-static, p-cpe:/a:amazon:linux:glibc-devel, p-cpe:/a:amazon...
Stack Overflow
stackoverflow.com › questions › 79041854 › glibc-version-issue-while-installing-npm-on-amazon-linux-2023
node.js - GLIBC version issue while installing npm on Amazon Linux 2023 - Stack Overflow
When I tried to check the current version of GLIBC on my Linux (ldd --version) it said 2.34. I'm utterly clueless at this point and need help! ... Not an exact duplicate, but basically the same issue - stackoverflow.com/q/72022527/2422776. Long story short, you either need a newer Linux version or an older Node.js version. ... @Mureinik I already have the latest version of Linux (Amazon Linux 2023) which should support up to Node v20 as per this document - docs.aws.amazon.com/lambda/latest/dg/… Also it shows the available GLIBC version on my Linux is 2.34.
Reddit
reddit.com › r/aws › al2023 does not have glibc 2.38?
r/aws on Reddit: al2023 does not have glibc 2.38?
May 21, 2025 -
I’m trying to deploy a .NET 9 AOT lambda on provided.al2023. I see a runtime exception that shows the bootstrapper cannot find glibc 2.38.
I’m building the app through GitHub actions using Ubuntu 24.04.
Anybody knows how to get around this issue?
Top answer 1 of 3
2
Oof, we had a similar hump to jump with nodejs 18 -> 20 (or was it 16 -> 18) and amazon linux 2. I'd advise filing an issue on al2023's tracker https://github.com/amazonlinux/amazon-linux-2023/issues?q=is%3Aissue asking for a bump but obviously that's going to have some interesting consequences taking glibc from 2.34 to 2.38 to just make it work natively. Looking at the lambda supported runtimes page https://docs.aws.amazon.com/lambda/latest/dg/lambda-runtimes.html , they must have figured out this was going to be a problem and built a temp workaround for now. Strangely enough, they haven't merged the branch for dotnet9 into main in the github repo ( https://github.com/aws/aws-lambda-base-images ) and I don't see a formal annoucement of .NET 9 lambda support yet ( https://aws.amazon.com/new/?whats-new-content-all.sort-by=item.additionalFields.postDateTime&whats-new-content-all.sort-order=desc&awsf.whats-new-categories=marketing-marchitecture%23serverless&whats-new-content-all.q=.NET&whats-new-content-all.q_operator=AND&awsm.page-whats-new-content-all=1 ). I wonder if someone has jumped the gun on the lambda documentation page before the release was supposed to go out.
2 of 3
2
Ha, 2.34 is all you get for the next 5 years. Like until al2023 release you had just amazon linux 2 with GLIBC 2.26 from 2017.