New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Conda activate resulting in PATH Errors and can't find mamba #1

Closed

Charlie-George opened this issue May 7, 2021 · 1 comment

Contributor

Charlie-George commented May 7, 2021

Conda is behaving strangely on CCB server because of conda install at /usr/condabin

after sourcing conda correctly, activating a new environment alters the path to no longer pick up correct conda or mamba from base env when in a different environment.

this is likely related to [https://github.com/PATH not set by conda activate conda/conda#9392] and multiple conda installs - particuarly /usr/condabin is added to path and conda recognises this before your proper condainstall

Contributor Author

Charlie-George commented May 7, 2021

Fix - add this line to .bashrc before sourcing conda

PATH=$(echo "$PATH" | sed -e 's/\/usr\/condabin://')

It removed /usr/condabin from path

Charlie-George closed this as completed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment