-
Notifications
You must be signed in to change notification settings - Fork 312
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
Python SDK incompatible with old GLIBC #2628
Comments
Hi, I'm the user who originally created this issue. My university cluster was updated to CentOS 8 finally but our GLIBC is still only 2.28. I'd really like to try out your tool so I'm wondering if there's any progress on this? |
@nchodosh when we tried to do this before we ran into some issues with build environments that were old enough to include the older glibc not having access to a recent enough libgtk3. However, I just found out that the packages we build for Is there any possibility you could use the Conda package instead of the pypi wheel? |
Ubuntu 18 is still stuck at glibc 2.28 (2.27?), can we get this on pip? Don't like conda installs. |
Exactly my situation as well. |
Same here; our cluster is still on CentOS 7. I'd imagine that most users on very old glibc versions (maybe not Ubuntu 18, but likely CentOS 7) care less about display support, especially given the excellent support for streaming w/re-run, if that makes things any easier! |
We actually made some good progress on this recently. The viewer is no longer linked into the wheel .so. Instead we bundle a separately built rerun executable which we launch via subprocess. This means these deps shouldn't be necessary for building the wheel anymore. I think this makes it possible to try moving the wheel-building environment to a manylinux container with an older glibc. I'll try taking a look at this again sometime soon. |
I noticed that our latest 0.17.0 wheels (linux x86) affectively use 2.29 max. We should consider advertising that version instead of 2.31 as we currently do.
|
We should be compatible with any glibc 2.17+, see: |
In short
The Rerun Python SDK is incompatible with GLIBC 2.17, and therefore CentOS 7.
I don't know what is our minimum required GLIBC version.
Problem
A user reported trying to use the Rerun Python SDK in a university cluster running CentOS 7, which uses GLIBC 2.17 (released 2012-12-25). The result:
The user further reports:
Solution
I think the solution is building the wheels on a machine with an old glibc version.
There are some clues here:
We should at least try, and we should also figure out what is the exact minimum GLIBC version required by the Rerun Python SDK.
The text was updated successfully, but these errors were encountered: