Replies: 1 comment 5 replies
-
|
Hi @qiutongs, You’re understanding it correctly. Right now, Adding flags to override those paths does make sense, especially if the goal is to generate a CDI spec that closely matches GPU DRA behavior. That would help with consistency across runtimes and make it easier to align with DRA-managed environments or custom container images. This would likely be a reasonable feature request: optional flags for container-side paths, with sensible defaults to preserve current behavior. It’s a niche need today, but very relevant for anyone working with DRA or non-standard container layouts. If this answer solve your all doubts so can you please mark my answer as solved |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
If I understand correctly, it is not supported today that container path of libs and binaries can be overridden for
nvidia-ctk cdi generate. Does it make sense to add new flags? I want to generate a CDI spec as close as to the one in GPU DRA.Beta Was this translation helpful? Give feedback.
All reactions