Great, thanks for the details, @simonhb!
My guess is that this is the problem - this version of glibc is over 10 years old. I set up a docker environment to test this hypothesis out in (the container version I am running here has glibc 2.13 installed in it):
docker run -it continuumio/miniconda3:3.9.0 /bin/bash \
-c "conda update conda -y -q \
&& conda info \
&& conda install wget -y -q \
&& wget https://data.qiime2.org/distro/core/qiime2-2021.4-py38-linux-conda.yml \
&& conda env create -n qiime2-2021.4 --file qiime2-2021.4-py38-linux-conda.yml"
This fails with the following error:
ResolvePackageNotFound:
- q2-demux 2021.4.0*
- nodejs >=15.14.0,<16.0a0
- __glibc >=2.17,<3.0.a0
- q2-diversity 2021.4.0*
- nodejs >=15.14.0,<16.0a0
- __glibc >=2.17,<3.0.a0
- q2-quality-control 2021.4.0*
- q2-taxa 2021.4.*
- nodejs >=15.14.0,<16.0a0
- __glibc >=2.17,<3.0.a0
- q2-feature-classifier 2021.4.0*
- q2-quality-control 2021.4.*
- q2-taxa 2021.4.*
- nodejs >=15.14.0,<16.0a0
- __glibc >=2.17,<3.0.a0
- q2-taxa 2021.4.0*
- nodejs >=15.14.0,<16.0a0
- __glibc >=2.17,<3.0.a0
- nodejs 15.14.0*
- __glibc >=2.17,<3.0.a0
Is there any chance you can chat with your sysadmin to see about getting a version of glibc that is a bit more modern? It looks like 2.17 should get the job done.
:qiime2: