-
Story
-
Resolution: Done
-
Medium
-
OSC 1.7.0
-
None
-
Upstream
-
3
-
False
-
None
-
False
-
Known Issue
-
Done
-
-
-
0
-
0.000
Both crio and configuration-remote.toml file needs to be updated to align with upstream changes.
Current config: https://github.com/openshift/sandboxed-containers-operator/blob/devel/config/peerpods/local/configuration-remote.toml
MC using the config - https://github.com/openshift/sandboxed-containers-operator/blob/devel/config/peerpods/mc-40-kata-remote-config.yaml
CRIO config - https://github.com/openshift/sandboxed-containers-operator/blob/devel/config/peerpods/mc-50-crio-config.yaml
Latest configuration-remote.toml: https://github.com/kata-containers/kata-containers/blob/main/src/runtime/config/configuration-remote.toml.in
CRIO config to be used
```
[crio.runtime.runtimes.kata-remote]
runtime_path = "/usr/bin/containerd-shim-kata-v2-tp"
runtime_type = "vm"
runtime_root = "/run/vc"
runtime_config_path = "/opt/kata/configuration-remote.toml"
privileged_without_host_devices = true
runtime_pull_image = true
allowed_annotations = [
"io.kubernetes.cri-o.Devices",
]
```
- links to
- mentioned on