Error in installing LTS version after trying latest version failure
Hello everyone,
I faced an issue when installing LTS version nodejs.
[ec2-user@phoenix ~]$ curl -fsSL https://rpm.nodesource.com/setup_lts.x | sudo bash -
## Installing the NodeSource Node.js 16.x repo...
Inspecting system...
- rpm -q --whatprovides redhat-release || rpm -q --whatprovides centos-release || rpm -q --whatprovides cloudlinux-release || rpm -q --whatprovides sl-release || rpm -q --whatprovides fedora-release
- uname -m
Confirming "el7-x86_64" is supported...
- curl -sLf -o /dev/null 'https://rpm.nodesource.com/pub_16.x/el/7/x86_64/nodesource-release-el7-1.noarch.rpm'
Downloading release setup RPM...
- mktemp
- curl -sL -o '/tmp/tmp.SunWxdtvqt' 'https://rpm.nodesource.com/pub_16.x/el/7/x86_64/nodesource-release-el7-1.noarch.rpm'
Installing release setup RPM...
- rpm -i --nosignature --force '/tmp/tmp.SunWxdtvqt'
Cleaning up...
- rm -f '/tmp/tmp.SunWxdtvqt'
Checking for existing installations...
- rpm -qa 'node|npm' | grep -v nodesource
Run sudo yum install -y nodejs to install Node.js 16.x and npm.
You may run dnf if yum is not available:
sudo dnf install -y nodejs
You may also need development tools to build native addons:
sudo yum install gcc-c++ make
To install the Yarn package manager, run:
curl -sL https://dl.yarnpkg.com/rpm/yarn.repo | sudo tee /etc/yum.repos.d/yarn.repo
sudo yum install yarn
[ec2-user@phoenix ~]$ sudo yum install -y nodejs Loaded plugins: extras_suggestions, langpacks, priorities, update-motd amzn2-core | 3.7 kB 00:00:00 Resolving Dependencies --> Running transaction check ---> Package nodejs.x86_64 2:18.2.0-1nodesource will be installed --> Processing Dependency: libc.so.6(GLIBC_2.28)(64bit) for package: 2:nodejs-18.2.0-1nodesource.x86_64 --> Processing Dependency: libm.so.6(GLIBC_2.27)(64bit) for package: 2:nodejs-18.2.0-1nodesource.x86_64 --> Finished Dependency Resolution Error: Package: 2:nodejs-18.2.0-1nodesource.x86_64 (nodesource) Requires: libm.so.6(GLIBC_2.27)(64bit) Error: Package: 2:nodejs-18.2.0-1nodesource.x86_64 (nodesource) Requires: libc.so.6(GLIBC_2.28)(64bit) You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest
You can see even I used LTS v16 version to install. The yum will still try the v18, which made me confused. Is there any easy way to switch to LTS version install?
Regards,
I am also having this issue on Amazon Linux 2 with Node 18.
Same
I have spent over 8 hours today trying to do this, this is driving me nuts. And total silence from NodeSource support.
Its because amazon linux 2 is locked to glibc version 2.26, anything that doesn't match it will fail.
please rename this issue to Does not work on Amazon Linux 2.... @JesusPaz is the above all correct?
I should also clarify, my issue is with node gallium (nsolid-v4.8.0-gallium-linux-arm64)
I've created an issue that's clearer about what's going on, this is not related to architectures https://github.com/nodesource/distributions/issues/1433
I think I found the problem, it started happening with version 4.7.0 when a newer version of GLIB_C was used to compile the LTS versions. This was obviously a mistake as it leaves Amazon Linux 2 users stuck in the cold. Version 4.6.3 should work.
I am also facing this issue now. when i have installed the node 18.14.2 on amazon linux2. Error: Package: 2:nodejs-18.14.2-1nodesource.x86_64 (nodesource) Requires: libc.so.6(GLIBC_2.28)(64bit) Error: Package: 2:nodejs-18.14.2-1nodesource.x86_64 (nodesource) Requires: libc.so.6(GLIBC_2.28)(64bit)
Hi @Cheng19031 Node18 requires glibc2.28 AMZN LINUX comes with glibc2.26. This must be reported on https://github.com/nodejs/node we only create and distribute pacakges based on NODEJS binaries. you may move to amazon linux 2022
Thank you for your reply. I have degraded to the lower version Node16, the problem solved temporarily. Coincidentally, I am also planning to use amazon linux 2022 recently.
As of today there is Amazon Linux 2023 which has support for node18, node19, node20
Please fix this I can't install version 20 or 18. Have to revert to v16.