How To
Summary
In most of the cases, Conductor creates and manages conda environments from GUI. But there are cases we need to install packagers to certain Conductor conda env from command line. In this case, we need to activate the conda env first before performing the package installation using conda.
Usually if there are other Anaconda deployment and envs you'll see the default base env like following:
[root@host ~]# conda env list
# conda environments:
#
/home/user/anacondadeployment/anaconda/envs/condaenv
base * /root/anaconda3
So the Conductor conda env is list there but without name with it - which means it's another Anaconda deployment. Following we need to specify the path of "activate" to Conductor conda env to actually activate desired env.
[root@host ~]# source /home/user/anacondadeployment/anaconda/bin/activate condaenv
(condaenv) [root@host ~]# conda env list
# conda environments:
#
base /home/user/anacondadeployment/anaconda
condaenv * /home/user/anacondadeployment/anaconda/envs/condaenv
/root/anaconda3
After that, we can see current env is "condaenv" from Conductor Anaconda deployment path. From here, you can use conda to manage packages in this Conductor conda env.
Document Location
Worldwide
Log InLog in to view more of this document
Was this topic helpful?
Document Information
Modified date:
27 November 2019
UID
ibm11102887