Hi all,
I have a problem when running a TF-TRT model which is ssd_mobilenet_v1
in a Docker container on JetPack 4.6.1. I was able to use one container of mine which includes the following components in every release starting from JetPack 4.3 to JetPack 4.5.1:
- nvcr.io/nvidia/l4t-base:r32.4.4
- CUDA 10.0
- cuDNN 7.1.6
- TensorRT 5.1.6
- TensorFlow 1.13.1
- Protobuf 3.8.0
Here is the error I get when my code tries to convert a saved_model.pb
to TensorRT plan and just before my script opens the camera for inference:
F tensorflow/contrib/tensorrt/log/trt_logger.cc:42] DefaultLogger Assertion failed: eglCreateStreamKHR != nullptr
dla/eglUtils.cpp:57
Aborting...
Aborted (core dumped)
I already have my env variables set as the follows:
LD_LIBRARY_PATH=/usr/local/cuda-10.0/targets/aarch64-linux/lib::/usr/lib/aarch64-linux-gnu/tegra/:/usr/lib/aarch64-linux-gnu/tegra/
PATH=/usr/local/cuda-10.0/bin/nvcc:/usr/local/cuda-10.0/bin:/usr/local/cuda/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
# dpkg -l | grep TensorRT
ii graphsurgeon-tf 5.1.6-1+cuda10.0 arm64 GraphSurgeon for TensorRT package
hi libnvinfer-dev 5.1.6-1+cuda10.0 arm64 TensorRT development libraries and headers
ii libnvinfer-samples 5.1.6-1+cuda10.0 all TensorRT samples and documentation
hi libnvinfer5 5.1.6-1+cuda10.0 arm64 TensorRT runtime libraries
hi python3-libnvinfer 5.1.6-1+cuda10.0 arm64 Python 3 bindings for TensorRT
ii python3-libnvinfer-dev 5.1.6-1+cuda10.0 arm64 Python 3 development package for TensorRT
ii tensorrt 5.1.6.1-1+cuda10.0 arm64 Meta package of TensorRT
ii uff-converter-tf 5.1.6-1+cuda10.0 arm64 UFF converter for TensorRT package
But I can not figure out what NVIDIA changed with the latest JetPack release that could brake a isolated, containerized application. A container should remain an isolated environment and I should be able to use it since there is no major changes between JetPack 4.5.1 and JetPack 4.6.1 that could prevent me doing this. Is there any chance there is a bug with the DLA codes in the new release since the source of the error points that direction?