Closed ehxan139 closed 1 year ago
I believe the problems arise when I followed the installation method mentioned on this blog post
A Faster Solver for Conda: Libmamba
However, while reading the official documentation , I realised that this is not the recommended method and has known issues.
May be it is better if you just remove or update this blog post.
Thanks @ehxan139, please note that the mamba CLI documentation you linked is the documentation of the main mamba project, if you would like to continue to use the conda
tool and make use of mamba behind the scenes, please follow the getting starting guide of the conda-libmamba-solver project.
I've reopened your issue since it might be a legitimate problem.
I have the same issue. I built an installer with constructor tool, with conda inside. After installation and activation, I have the same problem with conda install --offline (I want to use cache).
I don't have that problem with the classic solver.
I am assuming you are bundling packages built locally from using local channels in constructor
, which you didn't map to an online channel in anaconda.org. As a result, your private packages have a "channel" field that points to that private path, which is of course not available in the target machine.
conda-libmamba-solver
adds the channels burnt in the packages to make sure we get the relevant updates from them too. However, in your case, this channel will never be available, so it fails.
We have two options right now:
constructor
installer using the remap_channels
field to "convert" your private channel into a public one. This only makes sense if you are building your own variants of publicly available packages (e.g. python
).CONDA_LIBMAMBA_SOLVER_NO_CHANNELS_FROM_INSTALLED=1
in your installation configuration (you can have a conda-meta/state
file in your installation that sets that environment variable).That said, I'll add some logic to handle this better (we can check whether the channel exists or not before adding it to the list if it comes from a package and not the user list).
Thanks @jaimergp
Checklist
What happened?
I tried installing a random package with classic solver and it installed without any issues.
However, when I changed my solver to libmamba and tried the same command again then I am getting following errors,
Can you help me understand and resolve this issue please? Also, when I run the command conda config --show-sources with libmamba solver, then I get following ouput,
As you can see there is no sources mentioned here other than the usual "conda-forge" and "defaults. However, when I try to install any package I get following error message about an additional channel source "file:///tmp/conda-pkgs".
I do not understand that where "file:///tmp/conda-pkgs" is coming and showing in the available channel sources. Apparently error is coming from this file. Can you please look into this?
Conda Info
Conda Config
Conda list
Additional Context
No response