docs: CNT 1.20 updates - #455
Conversation
Documentation preview |
Signed-off-by: Mike McKiernan <mmckiernan@nvidia.com>
b37e09d to
10cf2a4
Compare
cdesiniotis
left a comment
cdesiniotis
left a comment
There was a problem hiding this comment.
Thank you @mikemckiernan. This is a really great start!
| Invalid requests fail with a clear error. | ||
| - JIT-CDI mode now honors the `nvidia-container-runtime.modes.jit-cdi.nvcdi-disable-hooks` configuration option. | ||
| You can disable individual CDI hooks for environments where a generated hook is unnecessary or incompatible. | ||
| - The NRI plugin can inject ordinary workload CDI devices outside the toolkit namespace. |
There was a problem hiding this comment.
I would move this bullet to under Enhancements to container-toolkit Container images as the NRI plugin is only used in that context.
| - Updating `config.toml` no longer reverts previously modified options to their defaults. | ||
| - CDI generation no longer adds an `update-ldcache` hook when it discovers no driver libraries. | ||
| This fix prevents containers from running an unnecessary hook and avoids failures on systems or modes that do not inject libraries. | ||
| - The toolkit installer now installs `nvidia-cdi-hook` instead of wrapping it with a shell script. |
There was a problem hiding this comment.
I would move this bullet to under Enhancements to container-toolkit Container images as the toolkit installer (nvidia-ctk-installer) is invoked in the container-toolkit container.
| `update-application-profile`, and `update-ldcache`. The deprecated `chmod` hook | ||
| is disabled by default. Use `all` to disable every hook. | ||
|
|
||
| The following command disables the application-profile and dynamic-linker cache |
There was a problem hiding this comment.
| The following command disables the application-profile and dynamic-linker cache | |
| The following command disables the update-application-profile and update-ldcache |
|
|
||
| This release of the NVIDIA Container Toolkit `v1.20.0` is a feature release. | ||
|
|
||
| ### Fixes and Features |
There was a problem hiding this comment.
One more fix to add to the list: NVIDIA/nvidia-container-toolkit#1969
| When CDI or JIT-CDI injects the GPU, the toolkit also limits EGL and Vulkan | ||
| visibility to the physical GPUs assigned to the container. For more information | ||
| and exceptional compatibility settings, refer to | ||
| [Graphics and OpenCL Workloads](cdi-support.md#graphics-and-opencl-workloads). |
There was a problem hiding this comment.
Note that limiting EGL and Vulkan visibility is not unique to CDI/JIT-CDI modes. It is an existing behavior in legacy mode, and we recently updated CDI/JIT-CDI to bring feature parity across all use cases.
There was a problem hiding this comment.
ok, proposed text change:
"Legacy mode limits EGL and Vulkan visibility to the physical GPUs assigned to
a container when the graphics or display driver capability is enabled.
The 1.20.0 release adds the same behavior to CDI and JIT-CDI modes through the
update-application-profile hook. This change provides feature parity across
the modes.
If the application-profile hook conflicts with an application, refer to
Disabling Hooks in JIT-CDI Mode."
Signed-off-by: Mike McKiernan <mmckiernan@nvidia.com>
Signed-off-by: Mike McKiernan <mmckiernan@nvidia.com>
4 participants
Review HTML: https://nvidia.github.io/cloud-native-docs/review/pr-455/container-toolkit/latest/release-notes.html