Skip to content

Conversation

@Josca
Copy link

@Josca Josca commented Oct 30, 2025

Description

Use up-to-date NVidia GPU operator Helm chart installation - updated parameters. Previous version doesn't work anymore as the chart was updated and the command didn't use --version parameter.

Link: https://docs.k0sproject.io/head/runtime/#using-nvidia-container-runtime

@Josca Josca requested review from a team as code owners October 30, 2025 12:40
@Josca Josca requested review from kke and makhov October 30, 2025 12:40
Comment on lines +216 to +217
--set "toolkit.env[0].name=CONTAINERD_CONFIG" \
--set "toolkit.env[0].value=/run/k0s/containerd-cri.toml" \
Copy link
Member

Choose a reason for hiding this comment

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

I wonder if these should point to the "real" containerd config instead of this k0s managed CRI merged one 🤔 I guess it boils down to what exactly the operator does with this.

This is what the docs say:

CONTAINERD_CONFIG
The path on the host to the top-level containerd config file. By default this will point to /etc/containerd/containerd.toml (the default location for containerd). It should be customized if your containerd installation is not in the default location.

Based on the above, I'd say this should point to /etc/k0s/containerd.toml which in turn imports the CRI config

Copy link
Author

Choose a reason for hiding this comment

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

I just tried the config and it worked out-of-the box.

@makhov
Copy link
Contributor

makhov commented Nov 18, 2025

Could you please sign off the commit?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants