Skip to content
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

Open
partouf opened this issue Nov 23, 2024 · 3 comments
Open

Upgrade OS? (new glibc require for newer node version) #47

partouf opened this issue Nov 23, 2024 · 3 comments

Comments

@partouf
Copy link
Member

partouf commented Nov 23, 2024

While trying to use node v22, the following error appears:

node: /lib/x86_64-linux-gnu/libc.so.6: version 'GLIBC_2.28' not found

So we can't run that node version yet.

Conan server runs Ubuntu 18

GLIBC 2.27-3ubuntu1.6 (says ldd --version)

@partouf
Copy link
Member Author

partouf commented Nov 23, 2024

Reading https://stackoverflow.com/questions/74836873/glibc-2-28-not-found - it seems the same applies to node v18

@partouf partouf changed the title New glibc? Upgrade OS? (new glibc require for newer node version) Nov 23, 2024
@partouf
Copy link
Member Author

partouf commented Nov 23, 2024

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).

@partouf
Copy link
Member Author

partouf commented Nov 23, 2024

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant