@@ -52,20 +52,21 @@ the TODO list.
52
52
The main reason for this split of functionality is to allow
53
53
NRI plugins for other types of sandboxes and for other container clients other than just for CRI containers in the "k8s.io" namespace.
54
54
55
- ## Enabling NRI Support in Containerd
55
+ ## Disabling NRI Support in Containerd
56
56
57
57
Enabling and disabling NRI support in containerd happens by enabling or
58
- disabling the common containerd NRI plugin. The plugin, and consequently
59
- NRI functionality, is disabled by default. It can be enabled by editing
60
- the ` [plugins."io.containerd.nri.v1.nri"] ` section in the containerd
61
- configuration file, which by default is ` /etc/containerd/config.toml ` ,
62
- and changing ` disable = true ` to ` disable = false ` . Once enabled, the
63
- NRI section should look something like this:
58
+ disabling the common containerd NRI plugin. Starting with containerd 2.0
59
+ The plugin, and consequently NRI functionality, is enabled by default.
60
+ It can be disabled by editing the ` [plugins."io.containerd.nri.v1.nri"] `
61
+ section in the containerd configuration file, which by default is
62
+ ` /etc/containerd/config.toml ` , and changing ` disable = false ` to
63
+ ` disable = true ` . The NRI section to disable NRI functionality should
64
+ look something like this:
64
65
65
66
``` toml
66
67
[plugins ."io .containerd .nri .v1 .nri" ]
67
- # Enable NRI support in containerd.
68
- disable = false
68
+ # Disable NRI support in containerd.
69
+ disable = true
69
70
# Allow connections from externally launched NRI plugins.
70
71
disable_connections = false
71
72
# plugin_config_path is the directory to search for plugin-specific configuration.
0 commit comments