Warp
Warp copied to clipboard
warpdotdev
Cannot install Warp on Red Hat Enterprise Linux release 8.9 (Ootpa) due to GLIBC 2.29 requirement
Discord username (optional)
No response
Describe the bug
I am trying to install Warp for the Linux on Red Hat Enterprise Linux release 8.9 (Ootpa). Installing the RPM results in the following error:
Updating Subscription Management repositories.
Red Hat Enterprise Linux 8 for x86_64 - Supplementary (RPMs) 202 kB/s | 3.8 kB 00:00
teams 187 kB/s | 1.9 kB 00:00
Red Hat Enterprise Linux 8 for x86_64 - AppStream (RPMs) 197 kB/s | 4.5 kB 00:00
vscode 135 kB/s | 1.5 kB 00:00
Red Hat Ansible Engine 2.9 for RHEL 8 x86_64 (RPMs) 165 kB/s | 4.0 kB 00:00
Red Hat Satellite Tools 6.9 for RHEL 8 x86_64 (RPMs) 210 kB/s | 3.8 kB 00:00
Red Hat Enterprise Linux 8 for x86_64 - BaseOS (RPMs) 217 kB/s | 4.1 kB 00:00
edge 73 kB/s | 1.5 kB 00:00
epel-rhel8-x86_64 84 kB/s | 2.3 kB 00:00
Error:
Problem: conflicting requests
- nothing provides libc.so.6(GLIBC_2.29)(64bit) needed by warp-terminal-v0.2024.02.20.08.01.stable_01-1.x86_64 from @commandline
- nothing provides libm.so.6(GLIBC_2.29)(64bit) needed by warp-terminal-v0.2024.02.20.08.01.stable_01-1.x86_64 from @commandline
(try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)
I have tried the AppImage as well which results in:
./Warp-x86_64.AppImage
./Warp-x86_64.AppImage: /lib64/libm.so.6: version `GLIBC_2.29' not found (required by ./Warp-x86_64.AppImage)
./Warp-x86_64.AppImage: /lib64/libc.so.6: version `GLIBC_2.29' not found (required by ./Warp-x86_64.AppImage)
./Warp-x86_64.AppImage: /lib64/libm.so.6: version `GLIBC_2.29' not found (required by /tmp/.mount_Warp-xSuRAAj/usr/bin/../lib/libsqlite3.so.0)
My GLIBC version is 2.28
ldd --version
ldd (GNU libc) 2.28
Copyright (C) 2018 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Written by Roland McGrath and Ulrich Drepper.
To reproduce
Download rpm or AppImage on RHEL 8.9 or a system with an older GLLIBC than 2.29. Then try to install Warp.
Expected behavior
No response
Screenshots
No response
Operating system
Linux
Operating system and version
Red Hat Enterprise Linux release 8.9 (Ootpa)
Shell Version
GNU bash, version 4.4.20(1)-release (x86_64-redhat-linux-gnu)
Current Warp version
v0.2024.02.20.08.01.stable_01-1
Regression
No, this bug or issue has existed throughout my experience using Warp
Recent working Warp date
Never :-|
Additional context
No response
Does this block you from using Warp daily?
Yes, this issue prevents me from using Warp daily.
Is this a Warp specific issue? (i.e. does it happen in Terminal, iTerm, Kitty, etc.)
Yes, this I confirmed this only happens in Warp, not other terminals.
Warp Internal (ignore): linear-label:b9d78064-c89e-4973-b153-5178a31ee54e
None
Hi @espenonvik I believe the requirement is due to the dependencies Warp uses, not due to a bug in Warp. So you'll have to upgrade your GLIBC version for Warp to render on your Linux distro.
Please upgrade your GLIBC version >= 2.31 (sudo dnf update -y glibc)and let us know if you still have issues starting Warp. If you cannot upgrade the version, please open a feature request to support the older version of GLIBC.
Hi @dannyneira, I have exactly the same env: RHEL 8.9 and glibc 2.28. AFAIK there is no way to upgrade glibc without upgrading to RHEL 9, which is not possible for me.
Same situation here, so providing a version that works with for glibc 2.28 would help a lot :)
Sorry about this blocker folks. A couple of possible workarounds are to run Warp in a RHEL9 container within RHEL 8.9 or try using glibc-compat.
👍
Leonid Gorelik - Chat @ Spike [2i6vri]
On March 11, 2024 at 20:48 GMT, Espen Ønvik Pedersen @.***> wrote:
Same situation here, so providing a version that works with for glibc 2.28 would help a lot :)
— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.Message ID: @.***>
Sorry about this blocker folks. A couple of possible workarounds are to run Warp in a RHEL9 container within RHEL 8.9 or try using glibc-compat.
Regarding glibc-compat - it generates only glibc headers.
My apologies folks, you may have to wait until the upgrade to RHEL9 (or another distro that meets the requirements) as RHEL8.9 is at the end of maintenance May 2024, It's unlikely we will support it.
Closing as this older distro doesn't meet the requirements and will likely not be supported. If we do support older systems we will post on our changelog and install docs.
We may bundle Warp for Ubuntu 18, so it may be possible to support RHEL 8.9 glibc 2.28 (since Ubuntu 18 uses glibc 2.27). Realistically though, this isn't a high priority right now as we're focused on stability more than supporting older distros.
@dannyneira We'd appreciate if you can update this issue if the support is added - thanks!
I am running RHEL9.4 which uses glibc 2.34, in a VMWare Fusion virtual machine on my Apple Silicon (aarch64) M1 Mac. When installing Warp via the aarch64 rpm download, I receive this error:
- nothing provides libm.so.6(GLIBC_2.35)(64bit) needed by warp-terminal-v0.2024.06.04.08.02.stable_02-1.aarch64 from warpdotdev (try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)
When I attempt to execute the AppImage download, I receive this error:
./Warp-aarch64.AppImage: /lib64/libm.so.6: version `GLIBC_2.35' not found (required by ./Warp-aarch64.AppImage)
The prior comments in this issue suggest that Warp supports RHEL9, but if it requires glibc 2.35 then I take it that RHEL9 is not really supported?
We may bundle Warp for Ubuntu 18, so it may be possible to support RHEL 8.9 glibc 2.28 (since Ubuntu 18 uses glibc 2.27). Realistically though, this isn't a high priority right now as we're focused on stability more than supporting older distros.
it would be really helpful to release a bundle for Centos 8. As there is alot users still using it.
