Open drewgilliam opened 2 months ago
I'm not too knowledgeable with alpine.
Have you tried: https://github.com/conda-forge/miniforge/issues/219
I'm running into this issue still in 24.9.0
It looks like there hasn't been a new tagged release for constructor since august.
Once 3.9.4 is tagged and released + this is merged into miniforge and released this bug should be closed.
Until then my hack is to run the following (make sure to replace system_glibc_version and int_system_glibc_version with your glibc version
sed -i \
-e 's|system_glibc_version=.*|system_glibc_version="2.39.0"|' \
-e 's|int_min_glibc_version=.*|int_min_glibc_version="02170"|' \
-e 's|int_system_glibc_version=.*|int_system_glibc_version="02390"|' "Miniforge3-$(uname)-$(uname -m).sh"
Unfortunately my latest release got caught in our scheduled brownouts..... grrr
but maybe you can try one of the pre-releases: https://github.com/conda-forge/miniforge/releases/tag/24.9.2-0
Solution to issue cannot be found in the documentation.
Issue
The introduction of
virtual_specs
in PR #626 causes an installation failure on alpine images as described in https://github.com/conda/constructor/issues/850. TLDR; theconda/constructor
GLIBC check for alpine images failed to locate the installed GLIBC version.This should be fixed in https://github.com/conda/constructor/pull/856.
Could you please issue a new release using the latest
conda/constructor
GLIBC version check?Installed packages
Environment info