Skip to content
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

Don't try to write SOLV cache in read-only directories #3312

Open
3 tasks done
jaimergp opened this issue Jun 6, 2024 · 1 comment
Open
3 tasks done

Don't try to write SOLV cache in read-only directories #3312

jaimergp opened this issue Jun 6, 2024 · 1 comment

Comments

@jaimergp
Copy link
Contributor

jaimergp commented Jun 6, 2024

Troubleshooting docs

  • My problem is not solved in the Troubleshooting docs

Anaconda default channels

  • I do NOT use the Anaconda default channels (pkgs/* etc.)

How did you install Mamba?

Other (please describe)

Search tried in issue tracker

writable read-only cache

Latest version of Mamba

  • My problem is not solved with the latest version

Tried in Conda?

Not applicable

Describe your issue

Comes from conda/conda-libmamba-solver#522

conda-libmamba-solver + libmamba 1.5.x cannot operate on read-only caches because loading via api.Repo(...) always tries to write the SOLV cache file back to disk, and fails to do so in the write permissions are not there:

File "/tmp/software/python/3.11.4/lib/python3.11/site-packages/conda_libmamba_solver/index.py", line 293, in _json_path_to_repo_info

    repo = api.Repo(self._pool, noauth_url, str(path_to_use), escape_channel_url(noauth_url))
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

RuntimeError: Permission denied

I think this line:

write_solv(solv_file);

should have some error handling because that write_solv() call is not critical to the repo loading. Nice to have, sure, but not required.

mamba info / micromamba info

libmamba 1.5.8

Logs

No response

environment.yml

No response

~/.condarc

No response

@jaimergp
Copy link
Contributor Author

Just learnt that this is solved in v2, so feel free to close if 1.x is not being maintained anymore.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant