Containers & Docker
Container Runtime Reference
Search container runtime concepts — OCI Runtime Spec, containerd, runc, gVisor sandboxing, Kata VM isolation, and Linux cgroups/namespaces.
No data is transmitted — everything runs locallyTool
About this tool
Container Runtime Reference
The Container Runtime Reference covers OCI Runtime Spec, containerd, runc, gVisor, Kata Containers, and Linux cgroups/namespaces container isolation primitives.
• Understand containerd vs Docker daemon before a Kubernetes node runtime change
• Look up gVisor use cases before evaluating it for a multi-tenant environment
• Reference cgroups vs namespaces before presenting container isolation to a team
• Find Kata Containers use cases before evaluating VM-based container isolation
Next step
Container Base Image Comparison — Compare container base images by size, compatibility, and attack surface for your runtime.
Open Container Base Image Comparison →
FAQ
What does this tool tell you?
The Container Runtime Reference covers OCI Runtime Spec, containerd, runc, gVisor, Kata Containers, and Linux cgroups/namespaces container isolation primitives.
What affects the result most?
OCI Runtime Spec: defines how container runtimes execute bundles — runc, crun implement this. containerd: high-level runtime used by Kubernetes — manages image pull, storage, and runc. runc: low-level OCI-compatible runtime — creates and runs containers from OCI bundles.
How should I use the result?
Use this tool to orient quickly to the concepts, field names, or values you are about to look up in a full specification or vendor documentation. It summarizes the common cases; the authoritative source remains whichever standard or vendor doc defines the values themselves.
Related tools