-
-
Notifications
You must be signed in to change notification settings - Fork 82
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
Install of 2.6.2 from conda-forge fails when was previously working #210
Comments
If you are trying to install |
As shown in my original post this build worked barely over a week ago and now does not. I'm hoping to get clarification on why. The requirement pinned to |
From
Am I misinterpreting your suggestion @izahn ? |
No, you have the right idea. See how it no longer says
? |
How about even starting with something simpler: |
In this case requirements.txt is a red herring. It's added on top of the base image which is At the risk of going slightly off topic here, ultimately it looks like there is a difference between 2.6.2 and 2.7.0. Does not work: CONDA_OVERRIDE_CUDA='11.2' mamba install tensorflow-gpu==2.6.2 (Errors with Works:
|
Also, fyi, there is a known bug (see #208) that
or
|
Also, I do realize the title of this issue is incorrect and that is my mistake. 2.6.2 is indeed available on conda-forge as is 2.7.0. I was looking mistakenly at the |
Right, well then everything has to be compatible with what is already installed in that environment or it won't work.
Of course, wouldn't be much point in having both version is they were the same :-)
But this is now about compatibility between |
That's a fair point ... since |
I've found it helpful to try to install the thing it says it can't and then keep going until it mentions something already in the environment. So here you could start with
and go from there. |
recent (global pinnings) changes include grpc_cpp and protobuf, I would start with these two --- the all-spark-notebook might be late (in case of protobuf) or early (in case of grpc_cpp) |
For context: the global pinning sets a universal version for certain dependencies (like protobuf) that many packages are compiled against. To increase this version, conda-forge runs a migration that builds all packages depending on (e.g.) protobuf against the new version (i.e. a transition period where there are packages against both the old and the new version), and once all packages are done, the migration is closed, and the global pin updated. The reason this is relevant and perhaps somewhat non-obvious is that eventually, after things have moved to a new global pin, all package builds following from then on will be compiled against the new version, and old package builds become impossible to install side-by-side with the newest packages that depend on the same shared libraries, but are compiled against a different ABI. |
thanks for the
|
The link is correct, scroll down to the Note about "How is cudatoolkit selected at install time" |
Though for users I guess https://conda-forge.org/docs/user/tipsandtricks.html#installing-cuda-enabled-packages-like-tensorflow-and-pytorch is better. |
The build output below is for a successful install of
tensorflow-gpu==2.6.2
from 10 days ago.As of today (2022-02-14), tensorflow-gpu 2.6.2 install now seems not to work despite nothing about the build parameters being changed.
What happened here?
The text was updated successfully, but these errors were encountered: