Skip to content
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

ImportError: libcublas.so.9.0: cannot open shared object file: No such file or directory #3548

Closed
noblerabbit opened this issue Feb 20, 2019 · 3 comments

Comments

@noblerabbit
Copy link

Hi,

I am having problems if I want to use pipenv to install tensorflow-gpu.

If I create virtual env in conda, and do "pip install tensoflow-gpu", works like a charm.

However if I do "pipenv install tensoflow-gpu", after I try to import it in python I get
"ImportError: libcublas.so.9.0: cannot open shared object file: No such file or directory"

I have CUDA Version 10.0.130.
/usr/local/ folders: bin cuda cuda-10.0 etc games include lib man sbin share src

I read online that I should install cuda 9 instead of 10, however, tensorflow-gpu in conda works just fine, so if possible I'd like to avoid downgrading.

What is the "goto" way to fix this? How can I set up the same configuration as conda?

Thanks!

@uranusjr
Copy link
Member

uranusjr commented Apr 3, 2019

Cuda 9.0 is an external dependency expected by Tensorflow, and Pipenv has not way to manage it if Tensorflow does not manage it. You’ll need to ask the Tensorflow team for help.

@uranusjr uranusjr closed this as completed Apr 3, 2019
@uranusjr
Copy link
Member

uranusjr commented Apr 3, 2019

Similar situation: tensorflow/tensorflow#15604.

@noblerabbit
Copy link
Author

To give some update.
Conda env has the option to export path (ie to the cuda library) during activation. Once I deactivate the env the path goes back to what it was before. This is how I handle different envs with different cuda libraries.
Here is the info how to do that: https://stackoverflow.com/questions/46826497/conda-set-ld-library-path-for-env-only

I stopped using pipenv because I could not find at the time how to do that. It should be possible...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants