Skip to content

Conversation

@elezar
Copy link
Member

@elezar elezar commented Jan 15, 2026

Here is a proposal for a cleanup of #1498

It includes some of the intial commits from #1521 and builds on that to ensure that the runtime is not configured if NRI is enabled. Note that the config options are moved to top-level flags since we don't propagate the NRI config to the runtime.

elezar and others added 5 commits January 15, 2026 11:48
Signed-off-by: Evan Lezar <elezar@nvidia.com>
Signed-off-by: Evan Lezar <elezar@nvidia.com>
This change adds an interface (and a basic type) for configuring a
target runtime from the nvidia-ctk-installer.

Signed-off-by: Evan Lezar <elezar@nvidia.com>
Signed-off-by: Tariq Ibrahim <tibrahim@nvidia.com>
Signed-off-by: Evan Lezar <elezar@nvidia.com>
Sources: cli.EnvVars("TOOLKIT_PID_FILE", "PID_FILE"),
},
&cli.BoolFlag{
Name: "enable-nri-in-runtime",
Copy link
Contributor

Choose a reason for hiding this comment

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

I prefer --enable-nri-plugin as it's more explicit in what it's trying to do

@tariq1890 tariq1890 force-pushed the nri-plugin-server branch 4 times, most recently from 9078cfe to f15030c Compare January 15, 2026 19:17
@elezar elezar closed this Jan 16, 2026
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.

2 participants