-
Notifications
You must be signed in to change notification settings - Fork 2
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
Upgrade OS? (new glibc require for newer node version) #47
Comments
Reading https://stackoverflow.com/questions/74836873/glibc-2-28-not-found - it seems the same applies to node v18 |
If we have to update the OS version, I wonder if it wouldn't be even better to also change to arm64? Trying dist-upgrade is probably dangerous in this case. Actual upgrade should be tested properly (node, conanproxy, python, conan v1, etc) with new AMI and launching and testing with a test instance. Reason I also would suggest to swap to arm64 is because there's nothing x64 specific to this instance (afaik) and we might also have to upgrade hardware specs due to future intensifying use of this instance (more binaries, Windows libraries, etc). |
cc @mattgodbolt I know I'm probably the only doing stuff on this server, but it's getting old and rusty - not sure how much time to invest into this just yet vs other matters. But it might be worth doing rather sooner than later. Will probably take some time to do right and require a migration plan due to the fixed disk swapping to new instance and making sure nothing breaks before that. |
While trying to use node v22, the following error appears:
So we can't run that node version yet.
Conan server runs Ubuntu 18
GLIBC 2.27-3ubuntu1.6
(says ldd --version)The text was updated successfully, but these errors were encountered: