-
Notifications
You must be signed in to change notification settings - Fork 74k
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
Understanding Could not find TensorRT
#62976
Comments
TF_USE_TENSORRT_STATIC
Could not find TensorRT
@tymorrow TensorRT installation might require additional steps or dependencies, particularly on specific platforms like Ubuntu. TensorRT is an NVIDIA-specific library optimized for NVIDIA GPUs. It might not be available on non-NVIDIA hardware or specific Linux distributions like Ubuntu due to package management differences. |
Hi @sushreebarsa, could you elaborate on why the warning does not appear on Windows or MacOS? I'm also wondering why the warning appears at all; is it specifically to tell me what you just said? Thank you for your time. |
Any update? Been getting the same issue for about a month now. This what i am getting:
I have manually installed TensorRT and still have the same error Here is my Dockerfile for reference:
|
Issue type
Others
Have you reproduced the bug with TensorFlow Nightly?
Yes
Source
binary
TensorFlow version
tf 2.12, 2.15, nightly
Custom code
No
OS platform and distribution
Linux Ubuntu 22.04, MacOS 12, Windows 2022
Mobile device
No response
Python version
3.8 - 3.10
Bazel version
No response
GCC/compiler version
No response
CUDA/cuDNN version
No response
GPU model and memory
No response
Current behavior?
A warning "Could not find TensorRT" is produced when importing TensorFlow on Ubuntu 22.04.
However, this warning does not appear on Windows 2022 and MacOS 12.
I would expect the behavior to be consistent across platforms unless their is an Ubuntu-specific reason.
This issue is intended to help me understand:
Additional remarks:
Thank you for your time!
Standalone code to reproduce the issue
Relevant log output
The text was updated successfully, but these errors were encountered: