You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Debian buster is seriously aging at this point; security updates have ended and LTS ends next year. Switching to FROM buildpack-deps:bullseye fixes the install if you are prepared to update your OS. (buildpack-deps:bookworm or even buildpack-deps:stable also work if you want to use latest stable Debian version.)
The root cause is that pip3 on buster is an antiquated pip version, 18.1. Our wheels are built for manylinux2014 (now known as manylinux_2_17) - support for that didn't come until pip 19.3.
If you must use buster, you can first update the pip version and then the wheels should download fine, as it's python 3.7 and glibc 2.28, which we do currently support.
Note that we are considering dropping 3.7 support soon in Drop Python3.7 support #7188 - another reason to consider upgrading from buster.
I haven't attempted to debug the exact error message in your OP, it's probably related to the old pip version not supporting PEP517 (that came in pip 19.0) .
Initial Checks
Description
I have a Dockerfile which fails to build on aarch64 - I assume it's because usually people install the wheels and maybe there aren't wheels?
Error:
Example Code
Selected Assignee: @lig
The text was updated successfully, but these errors were encountered: