[Question]: Intended Runtime Options Override Mechanism

Question:

what is the intended mechanism today for setting containerd runtime overrides when using the tookit installer?

asking since there does still appear to be a --runtime-config-override flag, but seems to be an unintended artifact of https://github.com/NVIDIA/nvidia-container-toolkit/pull/722 which followed its removal in a previous PR https://github.com/NVIDIA/nvidia-container-toolkit/pull/643#discussion_r1780736399 with rationale that it was unnecessary complexity.
https://github.com/NVIDIA/nvidia-container-toolkit/blob/357b970814261fb17d9b4991b1d2636bce71d442/cmd/nvidia-ctk-installer/container/runtime/containerd/containerd.go#L78-L84

the "inheritance" mechanism which reads from the default or fallback runtime block works sufficiently well, but is tied closer to node infra/provisioning, which doesn't feel ideal for dynamic installations.

hoping to either re-introduce the --runtime-config-override feature or note down a recommended stance on how this should be done (and remove the dead code). maybe externally-managed containerd drop-in configs are the right way to go but then thats implicitly tied to the chosen NVIDIA_RUNTIME_NAME and whatnot.

Start with cmd/nvidia-ctk-installer/container/runtime/containerd/containerd.go around the referenced flag and pkg/config/engine/containerd/config.go around the default or fallback runtime logic. Compare the current installer behavior with the linked PR discussions and determine whether runtime overrides should be supported or documented through another mechanism. Done means the project has an agreed, documented approach and the dead code or missing behavior is resolved.