Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bump github.com/NVIDIA/nvidia-container-toolkit from 1.17.0 to 1.17.2 #1068

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Nov 29, 2024

Bumps github.com/NVIDIA/nvidia-container-toolkit from 1.17.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:

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:

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

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.
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 compatibility score

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)

Bumps [github.com/NVIDIA/nvidia-container-toolkit](https://github.com/NVIDIA/nvidia-container-toolkit) from 1.17.0 to 1.17.2.
- [Release notes](https://github.com/NVIDIA/nvidia-container-toolkit/releases)
- [Changelog](https://github.com/NVIDIA/nvidia-container-toolkit/blob/v1.17.2/CHANGELOG.md)
- [Commits](NVIDIA/nvidia-container-toolkit@v1.17.0...v1.17.2)

---
updated-dependencies:
- dependency-name: github.com/NVIDIA/nvidia-container-toolkit
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added dependencies Issue/PR Pull about a dependency file maintenance Issue/PR to create or address a team project management need labels Nov 29, 2024
Copy link

copy-pr-bot bot commented Nov 29, 2024

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

@elezar elezar merged commit 2fa8f6f into release-0.17 Dec 3, 2024
7 checks passed
@elezar elezar deleted the dependabot/go_modules/release-0.17/github.com/NVIDIA/nvidia-container-toolkit-1.17.2 branch December 3, 2024 13:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Issue/PR Pull about a dependency file maintenance Issue/PR to create or address a team project management need
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant