-
-
Notifications
You must be signed in to change notification settings - Fork 286
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
Local CUDA installation not being detected #2428
Comments
This is expected behavior. Conda ships the entire CUDA Toolkit as Conda packages |
pip does not have this issue as:
|
The point to understand is that "detecting the system CUDA" is not design goal of how CUDA is distributed in conda-forge. It's not that conda can't see the system CUDA; it's not even looking. The only thing we take into account is the driver compatibility via the There have been similar asks in the past (e.g. conda-forge/cudatoolkit-feedstock#61) if you want to take a look. |
Right Since Conda is language agnostic. So users typically expect an install command to pull in everything they need (Python & C/C++) So the general approach has been to broadly ship things as Conda packages. CUDA packages are merely a subset that are also handled this way. Though it is not unique to them |
Conda-forge documentation
Installed packages
Environment info
Issue
Installing tensorflow package results to conda pulling the same cuda version as that of the system install. It appears that conda is not detecting it and resulting to duplication.
note that paths have also been exported to no avail
however normal pip install does not attempt to reinstall cuda toolkit and detects system cuda, so clearly this is a conda-forge issue not resolving library requirements.
The text was updated successfully, but these errors were encountered: