-
Notifications
You must be signed in to change notification settings - Fork 2
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
failed on clone and compile easy_pbr #3
Comments
I tried to figure out the aforementioned problem, but when I run the script, it said: I use GeForce RTX 2080 Ti Seems should support your environment. Sorry again for interrupt you from your busy time |
Thank you for letting me know of the issue. As for the NVRTC error, what script raised such error? Please let me know if the error persists. |
Thank you so much for your quick response. As I said, I figured out the git clone problem I mentioned previously, and now I can successfully compile and run the code on Tesla A100 GPU. However, I don't have too much access time to that GPU since it is on a shared server of my university. So, I tried to use the compiled image on our lab's server, which only has some GeForce RTX 2080 Ti and Quadro RTX 6000, which only support CUDA Version of 11.0. I saw your new Dockerfile the CUDA version is 11.1.1. And when I run By the way, when I noticed the CUDA version problem, I tried to modify your Dockerfile several times, sometimes, I can generate images successfully even compile easy_pbr and data_loaders. But I never successfully compile lattice_net with the modified Dockerfile generated image. |
Firstly, I want to think you so much for your good work!
Sorry to interrupt you from your busy time.
I met some problems on clone easy_pbr
Please make sure you have the correct access rights and the repository exists. fatal: clone of '[email protected]:aantron/better-enums.git' into submodule path '/workspace/easy_pbr/deps/better_enums' failed
And I tried to clone the deps by myself, it still didn't work.
I am not familiar with GitHub, if possible, could you push your compiled image into the docker hub?
The text was updated successfully, but these errors were encountered: