-
Notifications
You must be signed in to change notification settings - Fork 337
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.
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
Mamba command not found (make mamba command available outside base environment) #34
Comments
yep, indeed we need to figure out how to make the |
This seems tricky because ideally we would want
|
Actually there is another directory in the conda base environment called
‘condabin‘ which is where conda itself is adding a copy of the conda
executable to be available in all environments. I was planning to do the
same, but from the recipes build.sh
However, this would not work completely outside of conda.
…On Tue 9 Jul 2019 at 10:36, Xiao Yu ***@***.***> wrote:
This seems tricky because ideally we would want mamba to be in the user's
PATH even when there is no active conda environment (post conda deactivate)
as well so that mamba env create ... work regardless of which if any
conda env is active. In our build process I'm just linking mamba to a bin
dir which seems to work well:
ls -s "$(conda info --base)/bin/mamba" "/usr/local/bin/mamba"
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#34>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAGYCPSTDGP6ZSSAZ2ZTT3LP6SPANANCNFSM4HW3ZQ7A>
.
|
this is fixed for linux now -- need to confirm that it works on osx & win as well (win not yet released). |
fixed by putting a link to mamba in the |
is this fixed for Windows? I am still getting this error. |
yep, should be fixed on windows, too. What version do you have? Did you run |
I am using the latest version. I did try conda init but still the same error. |
can you post |
sorry for the late reply. It is working now, after reinstall. |
@wolfv I believe that does not work when one does not have write access to condabin, correct? I am on a shared cluster environment where the base environment and packages in general are managed centrally.
|
As a workaround adding |
for mambaforge on osx a simple |
For anyone on macOS using Catalina or newer and thus have |
Bumps [@actions/cache](https://github.com/actions/toolkit/tree/HEAD/packages/cache) from 1.0.7 to 1.0.8. - [Release notes](https://github.com/actions/toolkit/releases) - [Changelog](https://github.com/actions/toolkit/blob/main/packages/cache/RELEASES.md) - [Commits](https://github.com/actions/toolkit/commits/HEAD/packages/cache) --- updated-dependencies: - dependency-name: "@actions/cache" dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Where did you add this in bashrc? It says my base env is micromamba but I can't seem to run 'mamba' in the terminal anywhere. Strangely enough, all my packages and the environment is working fine and being recognized by VScode. |
I still cannot run mamba in another environment, runs only in base. Can anyone help ? Should I add to path environments or something ? |
Please create a new ticket using the issue template and show exactly what you did and what you expected |
This is still an issue. Installing with mambaforge-pypy first runs into the issue of missing DLLs. After manually copying the files to the correct location, mamba works in the miniforge base env, but is not found in an environment created with My workaround for now is this:
( cc @foobar41 maybe this helps you too ) The reason I made a new folder instead of adding |
I installed
minimamba
and create a minimalvoila
environment. The issue is that from the base environment I have the mamba command available, but whenever I activate thevoila
environmentmamba
is not available anymore...The text was updated successfully, but these errors were encountered: