Unable to activate conda or mamba environments

[kabilar]

Description

• I might be missing something obvious, but I am unable to activate a conda environment in the terminal on the current ansible deployment (i.e. production) and the DoEKS deployment (i.e. staging). This is the case for both existing conda environments and new environments (e.g. conda create -n test python=3.10).

• See error stack below. This is even the case after running conda init and then relaunching the terminal to run conda activate base.

  jovyan@jupyter-kabilar:~$ conda env list
  # conda environments:
  #
  base                  *  /opt/conda
  allen                    /opt/conda/envs/allen
  
  jovyan@jupyter-kabilar:~$ conda activate base
  
  CondaError: Run 'conda init' before 'conda activate'
  
  jovyan@jupyter-kabilar:~$ conda init
  no change     /opt/conda/condabin/conda
  no change     /opt/conda/bin/conda
  no change     /opt/conda/bin/conda-env
  no change     /opt/conda/bin/activate
  no change     /opt/conda/bin/deactivate
  no change     /opt/conda/etc/profile.d/conda.sh
  no change     /opt/conda/etc/fish/conf.d/conda.fish
  no change     /opt/conda/shell/condabin/Conda.psm1
  no change     /opt/conda/shell/condabin/conda-hook.ps1
  no change     /opt/conda/lib/python3.11/site-packages/xontrib/conda.xsh
  no change     /opt/conda/etc/profile.d/conda.csh
  no change     /home/jovyan/.bashrc
  No action taken.
  jovyan@jupyter-kabilar:~$ conda activate base
  
  CondaError: Run 'conda init' before 'conda activate'

[satra]

base is always the default, so no need to activate. the second is that conda init does not persist in jupyterhub right now. it has to do with how init's take place.

[kabilar]

Thank you, Satra.

[asmacdo]

Could we have the same result by by modifying the profile scripts in the base image?

ie

export CONDA_EXE="/path/to/conda/bin/conda"
export _CE_M=""
export _CE_CONDA=""
. "/path/to/conda/etc/profile.d/conda.sh"