You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+10Lines changed: 10 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -38,6 +38,16 @@ For CDI to work the following needs to be done:
38
38
39
39
### CRI-O configuration
40
40
41
+
In CRI-O CDI support is enabled by default. It is configured with the default `/etc/cdi, /var/run/cdi`
42
+
CDI directory locations. Therefore you can start using CDI simply by dropping CDI configuration files
43
+
in either of those directories, static configuration into `/etc/cdi` and dynamically updated one into
44
+
`/var/run/cdi`. If you are unsure of the configured directories you can run this command to find them
45
+
out:
46
+
47
+
```bash
48
+
$ crio config |& grep -B1 -A5 cdi_spec_dirs
49
+
```
50
+
41
51
### Containerd configuration
42
52
43
53
To enable and configure CDI support in the [containerd runtime](https://github.com/containerd/containerd) 2 configuration options `enable_cdi` and `cdi_spec_dirs` should be set in the `plugins."io.containerd.grpc.v1.cri` section of the containerd configuration file (`/etc/containerd/config.toml` by default):
0 commit comments