Bump github.com/NVIDIA/nvidia-container-toolkit from 1.15.0 to 1.17.2

[dependabot]

Bumps github.com/NVIDIA/nvidia-container-toolkit from 1.15.0 to 1.17.2.

Release notes

Sourced from github.com/NVIDIA/nvidia-container-toolkit's releases.

v1.17.2

NOTE: This release is a unified release of the NVIDIA Container Toolkit that consists of the following packages:

• libnvidia-container 1.17.2
• nvidia-container-toolkit 1.17.2

The packages for this release are published to the libnvidia-container package repositories.

What's Changed

• Fixed a bug where legacy images would set imex channels as all. This bug caused containers to fail when no NVIDIA_IMEX_CHANNELS environment variable was set for legacy images.

Full Changelog: NVIDIA/nvidia-container-toolkit@v1.17.1...v1.17.2

v1.17.1

NOTE: This release is a unified release of the NVIDIA Container Toolkit that consists of the following packages:

• libnvidia-container 1.17.1
• nvidia-container-toolkit 1.17.1

The packages for this release are published to the libnvidia-container package repositories.

What's Changed

• Fixed a bug where specific symlinks existing in a container image could cause a container to fail to start.
• Fixed a bug on Tegra-based systems where a container would fail to start.
• Fixed a bug where the default container runtime config path was not properly set.

Changes in the Toolkit Container

• Fallback to using a config file if the current runtime config can not be determined from the command line.

Full Changelog: NVIDIA/nvidia-container-toolkit@v1.17.0...v1.17.1

v1.17.0

This release includes updates for:

• NVIDIA CVE-2024-0134

To view any published security bulletins for NVIDIA products, see the NVIDIA product security page (https://www.nvidia.com/en-us/security/)

For more information regarding NVIDIA's security vulnerability remediation policies, see (https://www.nvidia.com/en-us/security/psirt-policies/)

---

This is a promotion of the v1.17.0-rc.2 release to GA.

NOTE: This release does NOT include the nvidia-container-runtime and nvidia-docker2 packages. It is recommended that the nvidia-container-toolkit packages be installed directly.

NOTE: This release is a unified release of the NVIDIA Container Toolkit that consists of the following packages:

• libnvidia-container 1.17.0
• nvidia-container-toolkit 1.17.0

... (truncated)

Changelog

Sourced from github.com/NVIDIA/nvidia-container-toolkit's changelog.

v1.17.2

• Fixed a bug where legacy images would set imex channels as all.

v1.17.1

• Fixed a bug where specific symlinks existing in a container image could cause a container to fail to start.
• Fixed a bug on Tegra-based systems where a container would fail to start.
• Fixed a bug where the default container runtime config path was not properly set.

Changes in the Toolkit Container

• Fallback to using a config file if the current runtime config can not be determined from the command line.

v1.17.0

• Promote v1.17.0-rc.2 to v1.17.0
• Fix bug when using just-in-time CDI spec generation
• Check for valid paths in create-symlinks hook

v1.17.0-rc.2

• Fix bug in locating libcuda.so from ldcache
• Fix bug in sorting of symlink chain
• Remove unsupported print-ldcache command
• Remove csv-filename support from create-symlinks

Changes in the Toolkit Container

• Fallback to crio-status if crio status does not work when configuring the crio runtime

v1.17.0-rc.1

• Allow IMEX channels to be requested as volume mounts
• Fix typo in error message
• Add disable-imex-channel-creation feature flag
• Add -z,lazy to LDFLAGS
• Add imex channels to management CDI spec
• Add support to fetch current container runtime config from the command line.
• Add creation of select driver symlinks to CDI spec generation.
• Remove support for config overrides when configuring runtimes.
• Skip explicit creation of libnvidia-allocator.so.1 symlink
• Add vdpau as as a driver library search path.
• Add support for using libnvsandboxutils to generate CDI specifications.

Changes in the Toolkit Container

• Allow opt-in features to be selected when deploying the toolkit-container.
• Bump CUDA base image version to 12.6.2
• Remove support for config overrides when configuring runtimes.

Changes in libnvidia-container

• Add no-create-imex-channels command line option.

v1.16.2

• Exclude libnvidia-allocator from graphics mounts. This fixes a bug that leaks mounts when a container is started with bi-directional mount propagation.

... (truncated)

Commits

• fa66e4c Merge pull request #802 from elezar/bump-release-v1.17.2
• aac7258 Bump version for v1.17.2 release
• 70ac1e2 Merge pull request #801 from elezar/fix-legacy-nvidia-imex-channels
• f774cee Fix NVIDIA_IMEX_CHANNELS handling on legacy images
• 1467f3f Merge pull request #786 from elezar/bump-release-v1.17.1
• ca9612a Bump version for v1.17.1 release
• 11e4af3 Merge pull request #784 from elezar/fix-config-file-path
• edf5d97 Fix bug in default config file path
• b03e942 Merge pull request #780 from elezar/add-config-fallback
• a918591 Fallback to file for runtime config
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Superseded by #679.