-
Notifications
You must be signed in to change notification settings - Fork 6
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
Install jaxlib from a Nextstrain-managed repository #119
Comments
An example of how the unofficial binary is not reliable: #173 (comment) |
I'm looking into building JAX locally. |
I have an unfinished attempt at victorlin/build-jax. Summarizing the progress here since I plan to focus on other things for now. The goal was to try to compile an AARCH64 version of JAX on a GitHub-hosted Linux runner (AMD64). I briefly tried building via Docker under emulation, which was unsuccessful. Even if it were successful, it would probably take longer than the maximum allowed GitHub Actions workflow run time. Then, I focused on cross-compiling since that has been done before. I attempted this first with then without Docker (for easier debugging of individual commands as GitHub Actions steps). With a 3.5 hour run time, I was able to build a file |
I just noticed that conda-forge includes an AARCH64 version of jaxlib (feedstock). It's not maintained by JAX developers, but at least looks more reliable than the status quo. We might not want to use it directly due to reasons described in #127 (comment), but it's one example that would benefit from using Conda in the image build. |
This is no longer necessary now that jaxlib version 0.4.18 includes Linux aarch64 wheels. I've pushed 85fe9a7 to try things out and will make a PR if it goes well. |
Originally from #50 (comment)
On the
linux/arm64
platform,jaxlib
is installed from a pre-built binary provided by an external GitHub user:docker-base/Dockerfile
Lines 172 to 179 in 960fb5b
We should look into building and repackaging this library ourselves for security and reliability reasons.
The text was updated successfully, but these errors were encountered: