nvidia-container-toolkit/cmd
Evan Lezar 3e77955c87
Some checks failed
CI Pipeline / code-scanning (push) Has been cancelled
CI Pipeline / variables (push) Has been cancelled
CI Pipeline / golang (push) Has been cancelled
CI Pipeline / image (push) Has been cancelled
CI Pipeline / e2e-test (push) Has been cancelled
Allow container runtime executable path to be specified
This change adds support for specifying the container runtime
executable path. This can be used if, for example, there are
two containerd or crio executables and a specific one must be used.

Signed-off-by: Evan Lezar <elezar@nvidia.com>
2025-04-04 10:57:31 +02:00
..
nvidia-cdi-hook [no-relnote] Fix QF1012: Use fmt.Fprintf(...) instead of WriteString(fmt.Sprintf(...)) lint errors 2025-04-02 14:18:32 +02:00
nvidia-container-runtime Rename test folder to tests 2025-01-23 11:46:14 +01:00
nvidia-container-runtime-hook [no-relnote] Fix QF1012: Use fmt.Fprintf(...) instead of WriteString(fmt.Sprintf(...)) lint errors 2025-04-02 14:18:32 +02:00
nvidia-container-runtime.cdi Add nvidia-container-runtime.cdi executable 2023-02-13 16:09:46 +01:00
nvidia-container-runtime.legacy Add nvidia-container-runtime.legacy executable 2023-02-13 16:09:46 +01:00
nvidia-ctk Allow container runtime executable path to be specified 2025-04-04 10:57:31 +02:00
nvidia-ctk-installer Allow container runtime executable path to be specified 2025-04-04 10:57:31 +02:00