-
Hi ! The config I used is this one, with the NRI conf coming from the containerd docs: machine
files:
- content: |
[plugins]
[plugins."io.containerd.nri.v1.nri"]
disable_connections = false
plugin_config_path = "/etc/nri/conf.d"
plugin_path = "/opt/nri/plugins"
plugin_registration_timeout = "5s"
plugin_request_timeout = "2s"
socket_path = "/var/run/nri/nri.sock"
path: /etc/cri/conf.d/20-customization.part
op: create The configuration is successfully merged, but the NRI socket at |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 2 replies
-
I ended up finding a way to make it work, by overwriting the whole machine:
files:
- content: |
version = 3
disabled_plugins = [
"io.containerd.internal.v1.tracing",
"io.containerd.snapshotter.v1.blockfile",
"io.containerd.tracing.processor.v1.otlp",
]
imports = [
"/etc/cri/conf.d/cri.toml",
]
[debug]
level = "info"
format = "json"
path: /etc/cri/containerd.toml
op: overwrite @smira is there a more elegant way to do this that I missed or is overwriting the whole containerd conf the only way to enable a disabled plugin ? |
Beta Was this translation helpful? Give feedback.
-
With #10106 merged (and backported to 1.9.2), NRI plugins can be enabled with a simple configuration change, and NRI plugins work out of the box. |
Beta Was this translation helpful? Give feedback.
With #10106 merged (and backported to 1.9.2), NRI plugins can be enabled with a simple configuration change, and NRI plugins work out of the box.