Skip to content

Conversation

@mikemckiernan
Copy link
Member

@mikemckiernan mikemckiernan commented Nov 12, 2024

@mikemckiernan mikemckiernan self-assigned this Nov 12, 2024
@mikemckiernan mikemckiernan added the documentation Issue/PR focused on fixing/editing/adding documentation bits label Nov 12, 2024
@github-actions
Copy link

Documentation preview

https://nvidia.github.io/cloud-native-docs/review/pr-127

The toolkit attempts to use the `containerd` command to determine the container runtime configuration on the host.
On these platforms, the `containerd` executable is not on the PATH and results in an error.

NVIDIA recommends installing v1.16.2 of the toolkit when you install or upgrade the Operator.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
NVIDIA recommends installing v1.16.2 of the toolkit when you install or upgrade the Operator.
NVIDIA recommends installing v1.17.1 of the toolkit when you install or upgrade the Operator.

-----------------

* On Rancher RKE2 and K3s, NVIDIA Container Toolkit v1.17.0 fails to start.
The toolkit attempts to use the ``containerd`` command to determine the container runtime configuration on the host.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

To be specific , it attempts to run the following commands depending on the container runtime used for the cluster

i. containerd config dump
ii. crio status config

Signed-off-by: Mike McKiernan <[email protected]>
@mikemckiernan mikemckiernan merged commit 6dcc374 into NVIDIA:main Nov 13, 2024
2 checks passed
@mikemckiernan mikemckiernan deleted the k3s-known-issue branch November 13, 2024 15:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Issue/PR focused on fixing/editing/adding documentation bits

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants