Evan Lezar

@AlexAshs sorry for the delay in getting back to you. Would you mind creating a new ticket and including the debug output from `/var/log/nvidia-container-toolkit.log`? This logging can be enabled by...

@Golchoubian could you enable debug logging in the NVIDIA Container CLI by uncommenting the line: ``` #debug = "/var/log/nvidia-container-toolkit.log" ``` in `/etc/nvidia-container-runtime/config.toml`, repeating the failed run, and then attaching the...

@minertom this is not something specific to the NVIDIA Container Toolkit. Is there a TensorRT repo / forum that you could post the question to?

@baehongjun0212 the `libnvidia-encode.so` and `libnvcuvid.so` are associated with a particular driver version and are injected into a container by the NVIDIA Container Toolkit when the container is run. This means...

@rogerlee6411 could you confirm that the NVIDIA OCI hook is present in the selected hooks directory? Also, if you remove the `nvidia-smi` command, does the container still error out or...

@solatis as @qhaas mentions, we currently symlink to `centos8` packages for all RHEL 8.* releases and as such specifying `centos8` as the distribution name when configuring the yum repositories would...

@sparr the CDI config file is driver specific, and as such providing a spec that will work across machines is tricky. Instead we are working on tooling that will generate...

Hi @eriklindahl @elgalu. We have just released [`v0.13.0`](https://github.com/NVIDIA/k8s-device-plugin/releases/tag/v0.13.0). This includes a fix to balance replicas more effectively. Please give it a go and let us know if you have any...

Hi @neggert. We have just released [`v0.13.0`](https://github.com/NVIDIA/k8s-device-plugin/releases/tag/v0.13.0). This includes a fix to ensure that the resource names are generated consistently for MIG profiles. Please give it a go and let...

THis should have been resolved. If not, please open a new issue against https://github.com/NVIDIA/nvidia-container-toolkit