-
Notifications
You must be signed in to change notification settings - Fork 117
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
build successfully, but container didn't start #58
Comments
Hi! I haven't tested image on windows. |
Preparing models... |
Have you tried running other GPU based containers on wsl2, like TensorFlow benchmarks, to verify your wsl2 is properly configured for GPU usage? |
Try running this sample: |
Run "nbody -benchmark [-numbodies=]" to measure performance. NOTE: The CUDA Samples are not meant for performance measurements. Results may vary when GPU Boost is enabled.
|
Hm, then TensorRT should work as expected. I can double check that latest published version of InsightFace-REST works out of the box, but unfortunately I can't help you with running it on Windows. |
I have checked building from scratch with clean clone from repo - everything works as intended on Ubuntu 20.04. Looks like it's WSL related problem. |
thanks, I have tested cpu version. it works fine.maybe there is somthing wrong with parameters in this case |
Quote from Nvidia page above:
This might be the case, since Though according to the same document there also might be issues with pinned memory required for TensorRT, and issues with concurrent CUDA streams. If pinned memory is also the issue you can try add |
thanks. i will try |
Hi! Any updates? Have you managed to run it under WSL2? |
sorry,I just see your reply. I will try. |
Looks like WSL2 just wasn't supported by TensorRT, but according to change log latest TensorRT version should support it. Try using 21.12 TensorRT image. |
i try 21.12 and 22.01TensorRT image, unfortunately,all failed. 21.12 report GPU error during getBestTactic, 22.01 report Cuda failure: integrity checks failed |
Have you tried running other GPU based containers on WSL2 to ensure everything is installed correctly? |
win11,wsl2,ubuntu18.04
How can I deal with it?
The text was updated successfully, but these errors were encountered: