Back to Blog
Conda python versions6/19/2023 ![]() ![]() ![]() RUN source /root/lsst_stack/loadLSST.bash & eups distrib install -t v22_0_1 astshim RUN source /root/lsst_stack/loadLSST.bash & eups distrib install -t v22_0_1 sconsUtils RUN rm /etc/profile.d/myenv.sh /etc/profile.d/conda.sh RUN conda config -add channels conda-forge &ĮNV LSST_CONDA_CHANNELS=“intel conda-forge” RUN echo “source /opt/conda/etc/profile.d/conda.sh & conda activate myenv” > /etc/profile.d/myenv.sh (this is not the whole Dockerfile before this, I install apt packages and set up my Intel-python conda environment) The following seems to be working for me, using your newinstall.sh branch (the newinstall.sh step finishes almost instantaneously it doesn’t try to install anything new into the conda environment!): Is there a way I can tell it, “No, really, use THIS python.”? (I say “environment”, but I’m just using the “base” conda environment.) When I tell newinstall.sh to use my /opt/conda, however, it is installing its own Python, which is even a different version than the one I gave it (3.8 vs 3.7). ![]() Second, my goal is to have the LSST software installed in the same conda environment as some other software, which is using the Intel Python stack (with MKL, Intel custom versions of numpy, etc). newinstall.sh -b -t -P /opt/condaĬollecting package metadata (current_repodata.json). newinstall.sh: line 672: /opt/conda/bin/python/bin/activate: Not a directory newinstall.sh -b -t -P /opt/conda/bin/python This does not seem to be true – newinstall.sh seems to add “bin/conda” to the end of the “-P” argument and expects that to be the conda program. I believe incorrectly implies that “-P” takes the path to the python executable to use. This page, Install with newinstall.sh and eups distrib - LSST Science Pipelines ![]()
0 Comments
Read More
Leave a Reply. |