-
Notifications
You must be signed in to change notification settings - Fork 368
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
v2 doesn't solve pytorch=2.3.1=py3.10_cuda11.8*
, but v1 does
#3699
Comments
Thank you for the report. Does the problem resolve if you install We need to have a more robust discovery of the version of CUDA used on the system. |
I'm on macOS so can't install nvidia-smi, but setting It must be something about the build string format because this one CLI variant does work with micromamba v2:
The commands behave quite robustly across different operating systems and machines, so feel free to copy/paste and run these dry-runs to debug. |
I forgot to mention in my previous message that I cannot reproduce the problem locally with micromamba 2.0.5 using the command and configuration you provide. In particular, the build string is properly picked in the
Full OutputCONDA_OVERRIDE_GLIBC=2.17 micromamba create --dry-run "pytorch=2.3.1=*_cuda11.8*" python=3.10 -c pytorch -c nvidia/label/cuda-11.8.0 -c nvidia -c conda-forge --platform=linux-64 -p ~/tmp/dry
Can you try setting |
Yes this last command you shared does work. The problematic one is the one I shared in the opening message, with the build string |
Troubleshooting docs
Anaconda default channels
How did you install Mamba?
Micromamba
Search tried in issue tracker
pytorch
Latest version of Mamba
Tried in Conda?
Not applicable
Describe your issue
Comes from this report: conda/conda-libmamba-solver#591
@rsxdalv reports that a certain install command that used to work with libmamba v1 doesn't work anymore with v2. I could reproduce with micromamba:
This command:
Works with v1.5.11:
Fails with v2.0.5:
mamba info / micromamba info
Logs
environment.yml
No response
~/.condarc
The text was updated successfully, but these errors were encountered: