You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I build a image with caffe, Cuda8.0, cudnn5, and vnc sever.
By command line way,
docker exec -it container_name bash
I run py-faster-rcnn with caffe. It worked well.
But by VNC way, I use jumpdesktop to connect the same container through VNC. I run the same demo. It reported error.
WARNING: Logging before InitGoogleLogging() is written to STDERR
E1228 06:30:11.450963 3340 common.cpp:104] Cannot create Cublas handle. Cublas won't be available.
E1228 06:30:11.451587 3340 common.cpp:111] Cannot create Curand generator. Curand won't be available.
E1228 06:30:11.451587 3340 common.cpp:111] Cannot create Curand generator. Curand won't be available.
F1228 06:30:11.452177 3340 common.cpp:142] Check failed: error == cudaSuccess (35 vs. 0) CUDA driver version is insufficient for CUDA run\
time version
The text was updated successfully, but these errors were encountered:
This doesn't sound like an issue with one of the images in this repo, but your own? Obviously something is breaking by using a remote desktop. It's worth trying a remote connection over SSH to see whether it's the remote connection or the desktop part. And next you should also try a different VNC program.
There are Dockerfiles in this repo to build kaixhin/cuda-caffe:8.0 and kaixhin/vnc, but nothing that combines the two, so I don't know what the problem you are facing. If you can provide a Dockerfile and a sequence of commands to let me reproduce the problem then maybe I can help. Additional info that would be helpful would include your host operating system and your GPU model.
I build a image with
caffe
,Cuda8.0
,cudnn5
, andvnc
sever.By command line way,
docker exec -it container_name bash
I run
py-faster-rcnn
withcaffe
. It worked well.But by
VNC
way, I usejumpdesktop
to connect the same container throughVNC
. I run the same demo. It reported error.The text was updated successfully, but these errors were encountered: