Open dsommers opened 1 month ago
This issue also appeared with codium-1.93.1.24256-el8.x86_64
Yes, since 1.93
, VSCodium uses node-20
which requires glibc-2.29
. I didn't expect to affect el8
.
The move is due to that I wasn't able to pack the app with node-16
(if I remember correctly due to electron).
But reh
and reh-web
are still shipping with node-16
.
You could use our AppImage (not available in 1.94, yet) or our flatpak.
So I will have to rename el8
to el9
...
Okay, so I have tried the flatpak in the past ... and that sandboxing didn't work well with clangd
at all - so lots of the IDE experience was lost. I can give the AppImage a try, but I'm not that happy about that approach - on large applications it takes considerably longer to start the app and it adds tons of various mount bindings.
But I do see that RHEL-8.9 does provide a nodejs:20
module.
# yum module reset nodejs
[...]
# yum module enable nodejs:20
[...]
# yum install nodejs
[...]
# node --version
v20.16.0
# cat /etc/redhat-release
Red Hat Enterprise Linux release 8.10 (Ootpa)
I now see that I'm running RHEL-8.10, not 8.9 as indicated. But that shouldn't make a big difference either way.
Node itself isn't necessarily the issue since unofficial builds support glibc-2.17
(https://unofficial-builds.nodejs.org/download/release/) but the libraries used like electron
, chromium
or node modules with native binaries.
I agree flatpak and AppImage aren't ideal for an IDE.
Upstream still appears to support RHEL8, can you not emulate the way they build and pack the app?
This was already resolved once, in issue #1760 but has re-appeared once again.
Desktop (please complete the following information):