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.
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?
are there any significant differences between Amazon Linux 2 and CentOS? I know amazon Linux 2 is built on CentOS and I am told has better networking performance but are the same packages available, does systemctl function the same are any pitfalls that I should be aware of?
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.
Please try
sudo yum clean all
sudo yum update
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
It seems like you are using v.18.0.0 which was the latest but not well-supported.
Try uninstalling that.
Copynvm uninstall 18.0.0
Install a version that is active.
Copynvm install 16.0.0
You should now be using v16 which should be well-supported.
Basically im trying to run a game but it requires at least glibc 2.38 but it seems debian only offers 2.36 at the moment. Any way i can get a newer vesion of it?
EDIT: ended up just downloading the windows version of the game and running it with wine, im an idiot and thought i was having a problem with the sound when i first downloaded, that's why i tried the linux binary, but when i ran it with wine again i found out that the game came muted by default and that i had to press + to get the volume up
I’m currently using GLIBC 2.35 on Ubuntu 22.04, and I want to update it (for gaming purposes).
I’m also aware that updating it isn’t as simple as typing:
“sudo apt update GLIBC yada yada”
or whatever, so I’m not entirely sure how to update it properly without bricking my install.
Any ideas on what to do?
Hello,
First off - I work with Windows - so my Linux knowledge isn't that great.
I read here:
Amazon Linux 2 FAQs
> " Q. How is kernel 5.10 different from kernel 4.14? "" From a security standpoint, customers benefit from WireGuard VPN that helps setup an effective virtual private network with low attack surface and allows encryption with less overhead. "
Ok from that I interpret that Wireguard is included w. kernel 5.10 however;
WireGuard VPN makes it to 1.0.0—and into the next Linux kernel | Ars Technica
^ That states that it was included from kernel 5.6.
Ok so I might just install it manually but checking which "dist" Amazon Linux 2 actually is using:
cat /etc/*release
NAME="Amazon Linux" VERSION="2" ID="amzn" ID_LIKE="centos rhel fedora" VERSION_ID="2" PRETTY_NAME="Amazon Linux 2" ANSI_COLOR="0;33" CPE_NAME="cpe:2.3:o:amazon:amazon_linux:2" HOME_URL="https://amazonlinux.com/" Amazon Linux release 2 (Karoo)
and googling;
What Is Amazon Linux 2? (linuxhint.com)
^ Ok so it is based on RHEL so I should follow the RHEL (7)-instructions here:
Installation - WireGuard
yum install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm https://www.elrepo.org/elrepo-release-7.el7.elrepo.noarch.rpm
Loaded plugins: extras_suggestions, langpacks, priorities, update-motd
epel-release-latest-7.noarch.rpm | 15 kB 00:00:00
Examining /var/tmp/yum-root-6UzwPp/epel-release-latest-7.noarch.rpm: epel-release-7-14.noarch
Marking /var/tmp/yum-root-6UzwPp/epel-release-latest-7.noarch.rpm to be installed
elrepo-release-7.el7.elrepo.noarch.rpm | 8.6 kB 00:00:00
Examining /var/tmp/yum-root-6UzwPp/elrepo-release-7.el7.elrepo.noarch.rpm: elrepo-release-7.0-5.el7.elrepo.noarch
Marking /var/tmp/yum-root-6UzwPp/elrepo-release-7.el7.elrepo.noarch.rpm to be installed
Resolving Dependencies
--> Running transaction check
---> Package elrepo-release.noarch 0:7.0-5.el7.elrepo will be installed
--> Processing Dependency: glibc = 2.17 for package: elrepo-release-7.0-5.el7.elrepo.noarch
amzn2-core | 3.7 kB 00:00:00
---> Package epel-release.noarch 0:7-14 will be installed
--> Finished Dependency Resolution
Error: Package: elrepo-release-7.0-5.el7.elrepo.noarch (/elrepo-release-7.el7.elrepo.noarch)
Requires: glibc = 2.17
Installed: glibc-2.26-55.amzn2.aarch64 (@amzn2-core)
glibc = 2.26-55.amzn2
Available: glibc-2.26-28.amzn2.0.1.aarch64 (amzn2-core)
glibc = 2.26-28.amzn2.0.1
Available: glibc-2.26-30.amzn2.0.1.aarch64 (amzn2-core)
glibc = 2.26-30.amzn2.0.1
Available: glibc-2.26-32.amzn2.0.1.aarch64 (amzn2-core)
glibc = 2.26-32.amzn2.0.1
Available: glibc-2.26-32.amzn2.0.2.aarch64 (amzn2-core)
glibc = 2.26-32.amzn2.0.2
Available: glibc-2.26-34.amzn2.aarch64 (amzn2-core)
glibc = 2.26-34.amzn2
Available: glibc-2.26-35.amzn2.aarch64 (amzn2-core)
glibc = 2.26-35.amzn2
Available: glibc-2.26-36.amzn2.aarch64 (amzn2-core)
glibc = 2.26-36.amzn2
Available: glibc-2.26-37.amzn2.aarch64 (amzn2-core)
glibc = 2.26-37.amzn2
Available: glibc-2.26-38.amzn2.aarch64 (amzn2-core)
glibc = 2.26-38.amzn2
Available: glibc-2.26-39.amzn2.aarch64 (amzn2-core)
glibc = 2.26-39.amzn2
Available: glibc-2.26-41.amzn2.aarch64 (amzn2-core)
glibc = 2.26-41.amzn2
Available: glibc-2.26-42.amzn2.aarch64 (amzn2-core)
glibc = 2.26-42.amzn2
Available: glibc-2.26-43.amzn2.aarch64 (amzn2-core)
glibc = 2.26-43.amzn2
Available: glibc-2.26-44.amzn2.aarch64 (amzn2-core)
glibc = 2.26-44.amzn2
Available: glibc-2.26-45.amzn2.aarch64 (amzn2-core)
glibc = 2.26-45.amzn2
Available: glibc-2.26-47.amzn2.aarch64 (amzn2-core)
glibc = 2.26-47.amzn2
Available: glibc-2.26-48.amzn2.aarch64 (amzn2-core)
glibc = 2.26-48.amzn2
Available: glibc-2.26-53.amzn2.aarch64 (amzn2-core)
glibc = 2.26-53.amzn2
Available: glibc-2.26-54.amzn2.aarch64 (amzn2-core)
glibc = 2.26-54.amzn2
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigestHm ok so "glibc" isn't available in the required version since it shows to already be at the latest version.
Ok so the alternative instructions for RHEL 7 worked however I can't install "wireguard-tools" since it isn't included in that repo?
Packages for jdoss/wireguard (copr.fedorainfracloud.org)
^ I only see "wireguard-dkms" and not "wireguard-tools"
Sorry for the WoT, would appreciate some clarification / help.
Best Regards
Update:
Running the ARM64-version of Amazon Linux 2 w. kernel 5.10 since I am using a "Graviton 2"-instance (ARM-based) if that might matter
1， yum install yum-utils.noarch
2， package-cleanup --cleandupes
then it will tell you something like this
--> Finished Dependency Resolution Error: Trying to remove "yum", which is protected You could try using --skip-broken to work around the problem ———————————————————————————————————————————— in case
glibc-common-2.12-1.149.el6.x86_64 is a duplicate with glibc-common-2.12-1.132.el6_5.4.x86_64 glibc-common-2.12-1.149.el6.x86_64 has missing requires of glibc = ('0', '2.12', '1.149.el6')
3， yum check dependencies
yum check dependencies Loaded plugins: fastestmirror glibc-common-2.12-1.149.el6.x86_64 has missing requires of glibc = ('0', '2.12', '1.149.el6') Error: check ['dependencies']
4， rpm -e --nodeps glibc-common-2.12-1.149.el6.x86_64
5， yum clean all
6， yum update -y
I had this issue and resolved by:
sudo package-cleanup --cleandupes
and then run the update again:
sudo yum update