-
Notifications
You must be signed in to change notification settings - Fork 348
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
Mamba fails to remove cudatoolkit #3120
Comments
The particular package, cupy, is not important to reproduce the error, anything I have tried that depends on cudatoolkit presents the same behavior |
1 task
Would be interested to know what Mamba devs think about this issue |
weiji14
added a commit
to pangeo-data/pangeo-docker-images
that referenced
this issue
Mar 8, 2024
scottyhq
pushed a commit
to pangeo-data/pangeo-docker-images
that referenced
this issue
May 21, 2024
* Bump CUDA from 11.8 to 12.0 Update Pytorch, Torchvision and Tensorflow to use CUDA 12.0 builds. Also bumped pytorch from 2.0.0 to 2.1.0, torchvision from 0.15.1 to 0.16.1 and tensorflow from 2.14.0 to 2.15.0 because lower versions only has CUDA 11.8 on conda-forge. * Pin to flax>=0.8.0 * Set with-cuda=12.0 flag on conda-lock lock * Set CONDA_OVERRIDE_CUDA environment variable Xref https://conda-forge.org/docs/maintainer/knowledge_base.html#cuda-builds * Regenerate conda-lock files for ml-notebook and pytorch-notebook Manually re-locking * Delete conda-lock.yml files for ml-notebook and pytorch-notebook * Revert "Delete conda-lock.yml files for ml-notebook and pytorch-notebook" This reverts commit 7658847. * Bump conda-lock from 2.3 to 2.5 Bumps [conda-lock](https://github.com/conda/conda-lock) from 2.3.0 to 2.5.5. - [Release notes](https://github.com/conda/conda-lock/releases) - [Commits](conda/conda-lock@v2.3.0...v2.5.5) * Bump conda from 23.11.0 to 24.1.2 Bumps [conda](https://github.com/conda/conda) from 23.11.0 to 24.1.2. - [Release notes](https://github.com/conda/conda/releases) - [Changelog](https://github.com/conda/conda/blob/master/CHANGELOG.md) - [Commits](conda/conda@23.11.0...24.1.2) * Try manually removing cudatoolkit from conda-lock.yml Xref mamba-org/mamba#3120 * Revert "Set CONDA_OVERRIDE_CUDA environment variable" This reverts commit 4d26a19. * Try removing asterisk in front of cuda120 build string * Depend on cuda-version=12.0 instead of matching cuda120 build string * Increase conda-lock timeout minutes from 20 to 30min * [condalock-command] autogenerated conda-lock files * Revert "[condalock-command] autogenerated conda-lock files" This reverts commit 12da355. * Keep cuda120 build string regex pattern Partial revert of 537c27f * Set cuda-version pin as >=12.0 instead of =12.0 Pin minimum version of CUDA to 12.0, instead of specifying exact pin on 12.0 * Add virtual-packages.yml to ml-notebook and pytorch-notebook Xref https://github.com/conda/conda-lock/tree/v2.5.7?tab=readme-ov-file#--virtual-package-spec * [condalock-command] autogenerated conda-lock files --------- Co-authored-by: pangeo-bot <pangeo-bot@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Troubleshooting docs
Anaconda default channels
How did you install Mamba?
Mambaforge or latest Miniforge
Search tried in issue tracker
cuda
Latest version of Mamba
Tried in Conda?
I do not have this problem with Conda, just with Mamba
Describe your issue
These commands work with conda:
conda create -n cupy cuda-version=11.8 cupy -y conda activate cupy conda install "cuda-version>12" -y
Their outputs being, concatenated:
However, the same sequence fails with mamba, as the dependency solver fails to decide to remove cudatoolkit.
The output in this case is:
mamba info / micromamba info
Logs
environment.yml
No response
~/.condarc
No response
The text was updated successfully, but these errors were encountered: