| 25 Apr 2025 |
 luke-skywalker | * I see.
If Ill have to I would probably opt for editing /var/run/cdi/nvidia-container-toolkit.json, but at this point I dont see a reason not to stick with 16.2 and update once the upstream issue is resolved.
| 13:08:17 |
 ereslibre | yeah, updating /var/run/cdi/nvidia-container-toolkit.json is flaky as I exposed it, it expects ldconfig to be present within the container at the specified path | 13:10:27 |
| luke-skywalker | good to know. well until I see a good reason not to and everything works as needed, I will stick with 16.2 for the time being then. | 13:13:16 |
| luke-skywalker | currently just testing out different cluster setups in my homelab (4x machines, 2x with nvidia GPU) so will be a bit until any real deployment... | 13:14:35 |
 connor (he/him) (UTC-7) | Kevin Mittman: I noticed the TensorRT binary archive for x86_64-linux (and only x86_64-linux) includes libnvinfer_builder_resource.so.10.9.0 and libnvinfer_builder_resource_win.so.10.9.0. Both are ~1.9 GB, and I'm wondering if libnvinfer_builder_resource_win.so.10.9.0 is relevant for x86_64-linux systems, and if so, what it does compared to libnvinfer_builder_resource.so.10.9.0. | 23:33:24 |
 Kevin Mittman | In reply to @connorbaker:matrix.org
Kevin Mittman: I noticed the TensorRT binary archive for x86_64-linux (and only x86_64-linux) includes libnvinfer_builder_resource.so.10.9.0 and libnvinfer_builder_resource_win.so.10.9.0. Both are ~1.9 GB, and I'm wondering if libnvinfer_builder_resource_win.so.10.9.0 is relevant for x86_64-linux systems, and if so, what it does compared to libnvinfer_builder_resource.so.10.9.0. Checking. Also that tarball doesn't conform to the "binary archive" format ... and 6.4GB | 23:48:23 |
| Kevin Mittman | As the name implies, seems to be for cross compilation, Linux -> Windows | 23:55:01 |
| 26 Apr 2025 |
| connor (he/him) (UTC-7) | Shouldn't it be in a different targets directory if it's for cross to another system? | 00:01:28 |
 hexa (UTC+1) | heads up | 19:52:11 |
| hexa (UTC+1) | current onnxruntime on unstable requires w+x, while the version on release-24.11 does not | 19:52:34 |
