Project-HAMi / HAMi

Heterogeneous AI Computing Virtualization Middleware
http://project-hami.io/
Apache License 2.0
983 stars 200 forks source link

Bump github.com/NVIDIA/nvidia-container-toolkit from 1.15.0 to 1.16.2 #515

Closed dependabot[bot] closed 3 weeks ago

dependabot[bot] commented 2 months ago

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

Release notes

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

v1.16.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

  • Exclude libnvidia-allocator from graphics mounts. This fixes a bug that leaks mounts when a container is started with bi-directional mount propagation.
  • Use empty string for default runtime-config-override. This removes a redundant warning for runtimes (e.g. Docker) where this is not applicable.

Changes in the Toolkit Container

  • Bump CUDA base image version to 12.6.0

Changes in libnvidia-container

  • Add no-gsp-firmware command line option
  • Add no-fabricmanager command line option
  • Add no-persistenced command line option
  • Skip directories and symlinks when mounting libraries

Full Changelog: https://github.com/NVIDIA/nvidia-container-toolkit/compare/v1.16.1...v1.16.2

v1.16.1

What's Changed

  • Fix bug with processing errors during CDI spec generation for MIG devices

Full Changelog: https://github.com/NVIDIA/nvidia-container-toolkit/compare/v1.16.0...v1.16.1

v1.16.0

This is a promotion of the v1.16.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:

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

Full Changelog: https://github.com/NVIDIA/nvidia-container-toolkit/compare/v1.15.0...v1.16.0

What's Changed

  • Promote v1.16.0-rc.2 to v1.16.0

Changes in the Toolkit Container

  • Bump CUDA base image version to 12.5.1

... (truncated)

Changelog

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

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.
  • Use empty string for default runtime-config-override. This removes a redundant warning for runtimes (e.g. Docker) where this is not applicable.

Changes in the Toolkit Container

  • Bump CUDA base image version to 12.6.0

Changes in libnvidia-container

  • Add no-gsp-firmware command line option
  • Add no-fabricmanager command line option
  • Add no-persistenced command line option
  • Skip directories and symlinks when mounting libraries.

v1.16.1

  • Fix bug with processing errors during CDI spec generation for MIG devices

v1.16.0

  • Promote v1.16.0-rc.2 to v1.16.0

Changes in the Toolkit Container

  • Bump CUDA base image version to 12.5.1

v1.16.0-rc.2

  • Use relative path to locate driver libraries
  • Add RelativeToRoot function to Driver
  • Inject additional libraries for full X11 functionality
  • Extract options from default runtime if runc does not exist
  • Avoid using map pointers as maps are always passed by reference
  • Reduce logging for the NVIDIA Container runtime
  • Fix bug in argument parsing for logger creation

v1.16.0-rc.1

  • Support vulkan ICD files directly in a driver root. This allows for the discovery of vulkan files in GKE driver installations.

  • Increase priority of ld.so.conf.d config file injected into container. This ensures that injected libraries are preferred over libraries present in the container.

  • Set default CDI spec permissions to 644. This fixes permission issues when using the nvidia-ctk cdi transform functions.

  • Add dev-root option to nvidia-ctk system create-device-nodes command.

  • Fix location of libnvidia-ml.so.1 when a non-standard driver root is used. This enabled CDI spec generation when using the driver container on a host.

  • Recalculate minimum required CDI spec version on save.

  • Move nvidia-ctk hook commands to a separate nvidia-cdi-hook binary. The same subcommands are supported.

  • Use : as an nvidia-ctk config --set list separator. This fixes a bug when trying to set config options that are lists.

  • [toolkit-container] Bump CUDA base image version to 12.5.0

  • [toolkit-container] Allow the path to toolkit.pid to be specified directly.

  • [toolkit-container] Remove provenance information from image manifests.

  • [toolkit-container] Add dev-root option when configuring the toolkit. This adds support for GKE driver installations.

Commits
  • a5a5833 Merge pull request #710 from elezar/update-changelog
  • 8e07d90 Update CHANGELOG.md for v1.16.2 release
  • 2aadbbf Merge pull request #709 from elezar/bump-version-v1.16.2
  • 88f9414 Bump version to v1.16.2
  • 53c2dc6 Merge pull request #705 from elezar/remove-libnvidia-contianer-update-check
  • 3121663 Merge pull request #708 from elezar/revert-check-symlink-resolution
  • 4b6de80 Merge pull request #707 from elezar/revert-no-persistenced-flag-by-default
  • dc2ccdd Revert "Merge pull request #696 from elezar/check-link-resolution"
  • 5145b0a Revert "Merge pull request #694 from elezar/add-opt-in-to-sockets"
  • a819cfd Revert "Merge pull request #703 from elezar/fix-no-persistenced-flag"
  • 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 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)
wawa0210 commented 2 months ago

@dependabot rebase

dependabot[bot] commented 3 weeks ago

Superseded by #586.