You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
Micromamba
Search tried in issue tracker
ssl verify
Latest version of Mamba
My problem is not solved with the latest version
Tried in Conda?
I have this problem with Conda as well, without using Mamba
Describe your issue
conda-forge's CI is now using micromamba to provision the base environment instead of Miniforge. v1 works perfectly, but v2 runs into a SSL certificate issue with git on Windows.
For example in this CI run (scroll to the bottom):
fatal: unable to access 'https://github.com/apache/arrow-testing.git/': error setting certificate file: /usr/ssl/certs/ca-bundle.crt
Troubleshooting docs
Anaconda default channels
How did you install Mamba?
Micromamba
Search tried in issue tracker
ssl verify
Latest version of Mamba
Tried in Conda?
I have this problem with Conda as well, without using Mamba
Describe your issue
conda-forge's CI is now using micromamba to provision the
base
environment instead of Miniforge. v1 works perfectly, but v2 runs into a SSL certificate issue with git on Windows.For example in this CI run (scroll to the bottom):
This can also be observed in staged-recipes during a
git fetch
command:Note that the path is very Unix-y despite the CI running on Windows.
Interestingly, this is also observed with Pixi. conda and micromamba v1 work correctly.
One can set
GIT_SSL_NO_VERIFY=true
as a workaround, but of course that's not ideal.mamba info / micromamba info
Logs
environment.yml
No response
~/.condarc
No response
The text was updated successfully, but these errors were encountered: