Skip to content

Conversation

@jgehrcke
Copy link
Contributor

@jgehrcke jgehrcke commented Feb 5, 2025

Without this patch, containerd starts up with an erroneous runc config and systemctl status containerd shows

Feb 04 13:15:38 k8s-device-plugin-cluster-worker containerd[1278]:
    time="2025-02-04T13:15:38.716063472Z" level=warning
    msg="failed to load plugin io.containerd.grpc.v1.cri"
    error="invalid plugin config: no corresponding runtime configured in `containerd.runtimes` for `containerd` `default_runtime_name = \"runc\""

We debugged this yesterday and @elezar recommended to switch to the stable release channel for the toolkit, and to use the --config-source=command arg when invoking nvidia-ctk runtime configure.

Also see NVIDIA/nvidia-container-toolkit#686.

@copy-pr-bot
Copy link

copy-pr-bot bot commented Feb 5, 2025

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.

@jgehrcke jgehrcke force-pushed the jp/containerd-config branch 3 times, most recently from c2d3362 to bf95303 Compare February 5, 2025 12:31
Signed-off-by: Dr. Jan-Philip Gehrcke <jgehrcke@nvidia.com>
Signed-off-by: Dr. Jan-Philip Gehrcke <jgehrcke@nvidia.com>
@jgehrcke jgehrcke force-pushed the jp/containerd-config branch from bf95303 to 911564b Compare February 5, 2025 12:36
@ArangoGutierrez
Copy link
Collaborator

/ok-to-test

@jgehrcke
Copy link
Contributor Author

jgehrcke commented Feb 6, 2025

You live, you learn. By merging things.

@jgehrcke jgehrcke merged commit 4a3238d into NVIDIA:main Feb 6, 2025
8 checks passed
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