-
Notifications
You must be signed in to change notification settings - Fork 25
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
conda with libmamba solver does not work in offline mode #522
Comments
Thanks for perhaps identifying a potential bug with the conda-libmamba-solver. Before we transfer this issue over to the applicable repository (https://github.com/conda/conda-libmamba-solver), I was wondering whether you have tried explicitly setting the For most Linux installations, this should be done automatically for you. Here's an example from an Ubuntu Server VM where conda is installed to the system location
|
Sorry, cut & paste has destroyed the formatting. I have the same envs dirs as you.
|
Thanks for the clarification. I was unfortunately unable to recreate this myself. @jaimergp, do you believe this belongs in the conda-libmamba-solver project as a bug? |
At least in your |
I have to add one important point: Reproducing the problem is not as easy as I've described. It depends on one more condition: the user running conda has to be a member of the group owning the conda installation (base environment) (but none of the directories are group writable). |
I've done some futher debugging. The behavior only depends on whether the file
|
I think (1) is related to conda-forge/miniforge#506. I'll need to check what we do about it in (2). Seeing It's added to the Those |
Ok, a little summary of the things we'll need:
It's not clear to me why libmamba needs to write anything while offline reading the cache.
I think it might be this step, where it always tries to write the SOLV cache. I created an issue and proposed a PR, but my C++ is limited. |
Just learnt that this is fixed in libmamba v2, so when a new CLS is released with this PR merged, we can close this issue. |
libmamba 1.5.11 includes this fix too now. |
Checklist
What happened?
We have an environment without connection to the internet with a shared Conda Python installation. Regular Python users do not have write access to the installation. They use
conda create ...
to create their Conda environments. With the classic solver it works fine. But with the libmamba solver it does not work.For the example below I created a small environment to reproduce the bug.
It's easy to reproduce. You only need a read only Conda installation.
Conda Info
Conda Config
Conda list
Additional Context
here comes the what I've done in my shell:
The text was updated successfully, but these errors were encountered: