Use drop-ins for containerd configuration when available

[mkjpryor]

As of v2.0.0 and config version 3, containerd supports a more advanced merge strategy for configuration that would allow the NVIDIA runtimes to be configured in their own file.

This avoids the need to modify /etc/containerd/config.toml, making the container toolkit installation less invasive and improving compatibility with tools like kubespray for long-running, bare-metal clusters that need to be able to receive in-place updates.

[mkjpryor]

I am willing to contribute code for this feature, but would appreciate some guidance on the best approach.

[elezar]

cc @tariq1890

[github-actions]

This issue is stale because it has been open 90 days with no activity. This issue will be closed in 30 days unless new comments are made or the stale label is removed. To skip these checks, apply the "lifecycle/frozen" label.

[elezar]

@mkjpryor this was added as a feature in the NVIDIA Container Toolkit v1.18.0 release and is now the default (see #1260). This was implemented in such as way so as to support older containerd versions.

Closing this issue. If the behavior of the feature is not as you expect or you're having problems, please create a new issue.