Skip to content

Conversation

@elezar
Copy link
Member

@elezar elezar commented Aug 28, 2025

When running the nvidia runtime in csv mode, we should not inject the enable-cuda-compat hook until we make the host driver version detection more robust on these platforms. As it is, the host driver version detection returns a version of 1.1 (the suffix of libcuda.so) meaning that CUDA forward compatibility will always be used in a container regardless of whether this is required.

This will be properly added to the generated CDI spec for CSV-based platforms as a follow-up. See #1271

This is a backport of #1270

When running the nvidia runtime in csv mode, we should not
inject the enable-cuda-compat hook until we make the host driver
version detection more robust on these platforms. As it is, the
host driver version detection returns a version of 1.1 (the suffix
of libcuda.so) meaning that CUDA forward compatibility will always
be used in a container regardless of whether this is required.

This will be properly added to the generated CDI spec for CSV-based
platforms as a follow-up.

Signed-off-by: Evan Lezar <[email protected]>
@elezar elezar added this to the v1.17.x milestone Aug 28, 2025
@elezar elezar self-assigned this Aug 28, 2025
@elezar elezar requested a review from ArangoGutierrez August 28, 2025 11:13
@elezar
Copy link
Member Author

elezar commented Aug 28, 2025

cc @agirault

Copy link
Collaborator

@ArangoGutierrez ArangoGutierrez left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM-Backport

@elezar elezar merged commit c20497a into NVIDIA:release-1.17 Aug 28, 2025
16 checks passed
@elezar elezar mentioned this pull request Sep 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants