You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What I'd like:
Currently, the nvidia-container-toolkit package provides, among other things, the nvidia-container-runtime-hook and nvidia-ctk. There are downstream builders that don't want/need nvidia-container-runtime-hook but still need nvidia-ctk. Since Bottlerocket NVIDIA variants still need the legacy nvidia-container-runtime-hook, it can't be deprecated and removed from the package thus we should vend nvidia-ctk as a subpackage of nvidia-container-toolkit so that downstreams get only what they need without breaking existing variants.
Any alternatives you've considered:
Vend both as they are today, even if downstreams don't need nvidia-container-runtime-hook.
The text was updated successfully, but these errors were encountered:
What I'd like:
Currently, the
nvidia-container-toolkit
package provides, among other things, thenvidia-container-runtime-hook
andnvidia-ctk
. There are downstream builders that don't want/neednvidia-container-runtime-hook
but still neednvidia-ctk
. Since Bottlerocket NVIDIA variants still need the legacynvidia-container-runtime-hook
, it can't be deprecated and removed from the package thus we should vendnvidia-ctk
as a subpackage ofnvidia-container-toolkit
so that downstreams get only what they need without breaking existing variants.Any alternatives you've considered:
Vend both as they are today, even if downstreams don't need
nvidia-container-runtime-hook
.The text was updated successfully, but these errors were encountered: