`uv` installed during `rye self install` does not run on `manylinux_2_17_aarch64`

[tonywu6]

Steps to Reproduce

1. docker run --rm -it quay.io/pypa/manylinux2014_aarch64 bash
2. curl -sSf https://rye.astral.sh/get | RYE_INSTALL_OPTION="-y" bash

Expected Result

Rye installs and bootstraps successfully.

Actual Result

Install fails with

.rye/uv/0.2.13/uv: /lib64/libm.so.6: version `GLIBC_2.27' not found (required by /home/vscode/.rye/uv/0.2.13/uv)
.rye/uv/0.2.13/uv: /lib64/libc.so.6: version `GLIBC_2.27' not found (required by /home/vscode/.rye/uv/0.2.13/uv)
.rye/uv/0.2.13/uv: /lib64/libc.so.6: version `GLIBC_2.25' not found (required by /home/vscode/.rye/uv/0.2.13/uv)
.rye/uv/0.2.13/uv: /lib64/libc.so.6: version `GLIBC_2.28' not found (required by /home/vscode/.rye/uv/0.2.13/uv)
error: Failed to create self venv using /home/vscode/.rye/py/cpython@3.12.3/bin/python3. uv exited with status: exit status: 1

Version Info

rye 0.35.0
commit: 0.35.0 (a1dbc56d4 2024-06-24)
platform: linux (aarch64)
self-python: not bootstrapped (target: cpython@3.12)
symlink support: true
uv enabled: true

Stacktrace

No response

[charliermarsh]

I need to look at how it chooses the uv binary. For manylinux_2_17 uv only supports the statically linked variant.

[charliermarsh]

Ahh it uses the GitHub Release artifacts. Ok, can fix.