Delete implicit in dockerfile #1288
Conversation
psbang
force-pushed
the
psbang-implicit
branch
from
0593cf7
to
d55f27a
Compare
|
It looks like our two PRs may be dependent on one another #1282 I'm going to merge both and see what happens. |
| @@ -172,7 +163,9 @@ RUN pip install spacy && \ | |||
| {{ if eq .Accelerator "gpu" }} | |||
| # Install GPU-only packages | |||
| # No specific package for nnabla-ext-cuda 11.x minor versions. | |||
| RUN pip install pycuda \ | |||
| RUN export PATH=/usr/local/cuda/bin:$PATH && \ | |||
There was a problem hiding this comment.
I read it as a solution in a stackoverflow somewhere, I'll make sure to add the links in next time.
There was a problem hiding this comment.
A solution for what? You are removing the package in the end no?
There was a problem hiding this comment.
I was getting "Failed building wheel for pycude" errors, I found a solution here: https://forums.developer.nvidia.com/t/cant-install-pycuda/238230
| RUN rm /opt/conda/bin/../lib/libcusolver.so.11 && ln -s /usr/local/cuda/lib64/libcusolver.so.11 /opt/conda/bin/../lib/libcusolver.so.11 | ||
| {{ else }} | ||
| RUN ln -s /usr/local/cuda/lib64/libcusolver.so.11 /opt/conda/bin/../lib/libcusolver.so.11 |
There was a problem hiding this comment.
@psbang Same here, I am a bit surprised to see a cuda related command for non-gpu image build... A comment would be helpful.
There was a problem hiding this comment.
In this one, the build was failing for CPU because the directory it was trying to delete did not exist, but for some reason, that directory did exist on the GPU build, so this was the only way I was able to make it build successfully.
There was a problem hiding this comment.
Do you remember what process was trying to delete this directory? The underlying issue is likely that we were running a command that shouldn't have been run in the CPU and was missing the {{ if eq .Accelerator "gpu" }} guard.
There was a problem hiding this comment.
Line 643 in the updated file, I didn't change that, I just added the if-else statements around it.
Link to discussion: https://chat.kaggle.net/kaggle/pl/616sq69n53d4pg6puf3n97xxuo
https://b.corp.google.com/issues/295382867