User cannot activate environment from central installation -

[David S]

I just created a conda environment in a centrally administered conda install. User's won't have write permission the central install. However when I try to activate the environment as a user, I get:

Cannot activate environment bash.
User does not have write access for conda symlinks.

I have done this kind of thing before, but now I am using a newer version of conda - namely  4.1.3.

As I recall, there is nothing special I do to setup a central conda install except make a .condarc file in the root dir for the miniconda install. Users just put the bin subdir to this prefix in the front of their path and they are good to go, right?

 This is what I did from the central installation account:

psreldev) psdev106: ~ $ conda -V
conda 4.1.3
(psreldev) psdev106: ~ $ conda create -n boost boost python=2.7
Fetching package metadata ...................
Solving package specifications: ..........


Package plan for installation in environment /reg/g/psdm/sw/conda/inst/miniconda2-dev-rhel5/envs/boost:


The following NEW packages will be INSTALLED:


    boost:      1.60.0-py27_0 defaults
    icu:        54.1-0        defaults
    openssl:    1.0.2h-1      defaults
    pip:        8.1.2-py27_0  defaults
    python:     2.7.11-0      defaults
    readline:   6.2-2         defaults
    setuptools: 23.0.0-py27_0 defaults
    sqlite:     3.13.0-0      defaults
    tk:         8.5.18-0      defaults
    wheel:      0.29.0-py27_0 defaults
    zlib:       1.2.8-3       defaults


Proceed ([y]/n)? y


Linking packages ...
[      COMPLETE      ]|#######################################################################################################################################| 100%
No psutil available.
To proceed, please conda install psutil#
# To activate this environment, use:
# $ source activate boost
#
# To deactivate this environment, use:
# $ source deactivate
#
(psreldev) psdev106: ~ $