-
-
Notifications
You must be signed in to change notification settings - Fork 403
miniforge3 tries to access anaconda.org when creating a conda environment #784
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
Comments
good luck, we host on anaconda.org. work with your IT. |
you can make your own mirror.... |
Reopening because: It would be interesting to document how your IT works around this. Perhaps there is something that can be shared to the community. But today, Anaconda.org supplies us with storage space and plenty to tech support. it can't be ignored. |
@hmaarrfk - Thank you for explaining the dependency and for linking to the blog post. I will share this information and add any updates here. |
@hmaarrfk - Quick follow-up: If IT were to block only |
I'm not sure please troubleshoot with them. |
I am not 100% sure, but I guess that by using
should avoid to contact anaconda.org at all. See https://prefix.dev/blog/towards_a_vendor_lock_in_free_conda_experience for more info. |
Comment:
The issue:
While working on a system that has anaconda.org blocked by IT, creation of a conda environment fails because miniforge3 attempts to connect to https//conda.anaconda.org/conda-forge/osx-64. Both
conda config --show channels
andconda config --show-sources
show that the only channel in the config isconda-forge
. Is there a way to avoid contacting anaconda.org?The command:
The portions of the error mentioning anaconda:
The text was updated successfully, but these errors were encountered: