cri-tools
v1.37.0 open-sourceThe section your link pointed to isn't on cri-tools's page any more, so we've brought you to the top.
The cri-tools project provides command-line and validation tools for the Kubelet Container Runtime Interface (CRI).
CRICTL_CREDS='myuser:mypassword' crictl run container-config.json pod-config.json crictl metricdescs critest --websocket-attach --websocket-exec --websocket-portforward crictl metricdescs crictl update --oom-score-adj 500 <container-id> crictl logs --stream stderr <container-id> crictl exec --tls-ca /etc/cri/ca.crt --tls-cert /etc/cri/client.crt --tls-key /etc/cri/client.key --tls-server-name cri-runtime <container-id> /bin/sh crictl --profile-cpu /tmp/crictl-cpu.pprof stats crictl run --pull-timeout 60s container-config.json pod-config.json crictl exec --transport websocket <container-id> sh crictl images --filter dangling=true crictl events --container-id <container_id> crictl runtime-config crictl metricsp crictl config list crictl circt config --list critest --benchmarking-params-file=custom-bench.yaml critest --benchmarking-output-dir=/var/log/critest-benchmarks critest --benchmarking-params-file /path/to/params.yaml --benchmarking-output-dir /tmp/benchmarks critest --benchmarking-params-file /path/to/custom-params.yaml critest --benchmarking-output-dir /var/log/critest-benchmarks crictl statsp --pod-sandbox-id <POD_SANDBOX_ID> CRICTL_AUTH='Bearer <token>' crictl pull <registry>/<image>:<tag> crictl ps -r critest --test-images-file /path/to/custom-images.yaml crictl --timeout 30s create sandbox-id container-config.json sandbox-config.json crictl ps -s created crictl rmi --prune crictl container run --image nginx:latest crictl rm -f -a crictl rmi -a crictl imagefsinfo crictl ps --image nginx:latest crictl info -q crictl pods --namespace production --name nginx crictl ps --namespace kube-system --name etcd crictl ps -q export CONTAINER_RUNTIME_ENDPOINT=unix:///run/containerd/containerd.sock export IMAGE_SERVICE_ENDPOINT=unix:///run/containerd/image.sock crictl images crictl stats crictl config --help crictl logs --since 10m --timestamps <container_id>
Summary
cri-tools is an open-source command-line toolset, free to use, bundling crictl for inspecting a running container runtime and critest for validating that a runtime correctly implements the Kubelet Container Runtime Interface. It runs as a binary on the node alongside the kubelet, and is aimed at the people who build or operate CRI-compatible runtimes (containerd, CRI-O and similar) rather than application developers deploying workloads. Recent releases add OTELOTELAn open standard and set of tools for collecting traces, metrics and logs from applications. It lets services export observability data without tying instrumentation to one monitoring vendor. tracing flags, TLS-secured exec/attach/portforward sessions, and a metricdescs subcommand for discovering what metrics a runtime exposes, reflecting its role as the reference debugging layer the Kubernetes project itself maintains for CRI compliance. It follows Kubernetes's own minor-version release cycle, and with 155 contributors and a release cut 32 days ago, it is actively maintained.
The cri-tools project provides command-line and validation tools for the Kubelet Container Runtime Interface (CRI).
How cri-tools helps
What is actually running on this node right now, pod by pod and container by container?
lists every pod, container, and image the runtime currently knows about, independent of what the Kubernetes API server thinks is scheduled there
Why is a container on this node behaving differently than the runtime itself reports?
inspects and execs directly into the container through the runtime's own interface, bypassing the kubelet so the runtime's view can be compared against the kubelet's
Is a new or patched container runtime actually implementing the interface kubelet expects?
runs a conformance suite against the runtime's CRI endpoint and reports which required behaviors pass or fail against the spec
Where did a container's output go, and can it be recovered after the fact?
pulls stdout and stderr logs straight from the runtime, including reopening rotated log files or isolating a single stream
Which images and resources on a node are actually consuming space or memory?
queries the runtime for image lists, per-container stats, and CPU/memory/swap usage without going through the API server
Did a recent change to a runtime's CRI implementation break something a previous version supported?
runs the same validation suite against both versions and shows which spec checks now fail that used to pass
Languages
Command line
No command matches.
| option | found in | since | description |
|---|
Values are placeholders taken from each option’s declared default. Nothing is executed here — the output shown is a recording of a run that already happened.
Score card
-
Shipping velocity releases a month, last 12 months
-
Documentation quality release-notes rubric, 0–100
-
Breaking-change discipline how rarely a release breaks users, and notice given
-
Maintenance risk quiet time against its own cadence, maintainers
-
Innovation & surface new capabilities, API and MCP surface
- Community health
-
Contributor trend distinct committers, this year against last
-
Maintainer concentration bus factor now against a year ago
-
Issue backlog trend issues closed per issue opened, 12 months
-
Responsiveness median time to a maintainer’s first reply
Nine scores for cri-tools, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.
Score cards are part of every paid plan.
See plans → Already subscribed? Sign in →Trajectory
Blank means never measured; nothing here is a filled-in zero.
Peer standings are included with Researcher and Business. See how this tool ranks against its competitors, using data we don't publish anywhere else.
See plans →Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.
How this is scored
- Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
- Documentation quality — the release-notes rubric published on the analytics page, unchanged.
- Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
- Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
- Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
- Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
- Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
- Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.
Release-note detail over time
See how much detail cri-tools puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.
Checking release-note history…
Website history
kubernetes.io, every changeKubernetes's home page and 22 more pages as they looked each month from August 2021 to October 2026: 33 renders, 4 changes of tagline or palette. Step through them, play them, or put any two months side by side.
Website history is included with Researcher and Business.
See plans → Already subscribed? Sign in →← → or h l a month · Shift a year · [ ] previous / next change · Space play · 1 2 3 page · T whole page · C compare · F full size
← → or h l the right month · Shift the left · S swap · W wipe · T whole page · Esc back
Rebranding timeline
Dates bound when a change appeared between captures. Possible rebrands are AI suggestions; a redesign alone does not establish a rebrand.
Releases
35 entries
No entries match these filters.
- September 20261
- April 20261
- August 20251
- April 20251
- December 20241
- August 20241
- April 20241
- December 20231
- August 20231
- July 20231
- April 20231
- March 20231
- December 20221
- August 20221
- May 20223
- January 20221
- August 20211
- April 20211
- January 20211
- August 20201
- December 20191
- September 20191
- July 20191
- March 20191
- December 20181
- September 20181
- July 20181
- June 20181
- May 20181
- March 20181
- December 20171
- September 20171
- June 20171
Project health
Issue, contributor and maintainer activity in kubernetes-sigs/cri-tools, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.
- Contributors 14 −3 vs prior 12 months
- Maintainers 2 +1 joined · −0 left, last 12 months
- Bus factor 1 committers behind half the commits
- Community-filed 86% of issues opened, last 12 months
- Median time to close 27 days first maintainer reply 28 hours
- Open backlog 6 of 422 issues ever filed
- Issues opened / month 1 · 0 communitymaintainers
- Open backlog 6
- Contributors / month 2
- Commits / month 7
- Stars 2,014
- bugs 29%
- features 28%
- other 43%
Counts from the project's public repository and git history; no individuals are identified. Maintainers are the committers covering 80% of the last year's commits. how we measure this
Libraries its release ships
What its latest release locks, checked against known advisories.None of its release's images build from a lockfile we can read.
Add the badge to your README
Maintain this project? The badge links readers straight to this page, so they can follow every release here.