cri-o
reference corpus · status live · domain OPS (Operations and SRE) · lane A · refresh pinned · tags GLOBAL · CONTAINERS · CRI · KUBERNETES · RUNTIME
What an agent uses it for
An agent running a Kubernetes-dedicated container runtime queries this for CRI-O's CRI implementation and OCI integration.
curl -fsSLO https://raw.githubusercontent.com/xerj-org/xerj/corpus-hub/tools/xerj-code/hub/cri-o.jsonxerj corpus add --from ./cri-o.jsonxerj corpus index cri-o then xerj code cri-o "your question"Needs the xerj CLI and a local node running; the copy prompt covers both, checks each step, and shows how to stop only the node you started. No shell: the MCP tool xerj_code_search with corpus: "cri-o", once the corpus is indexed on the node.
Sources and pins
| source | pin | licence | size | review note |
|---|---|---|---|---|
| cri-o | 617265f33955 | Apache-2.0 | 100.8 MB / 10,130 files | licence host-verified (ok-spdx): Apache-2.0 |
100.8 MB across 10,130 files. Added 2026-10-13.
Rights
Apache-2.0. Redistribution permitted with attribution per the licence review. The review block records a human opening each licence file at the pin. Detector output is a hint, never the verdict.
Retrieval spot-check (G7)
Not yet spot-checked. Queries are pre-registered in the registry before grading.