Container RuntimesMediumSingle Choice
Container Runtimes Question
Statement
Which group of container runtimes provides additional sandboxed isolation and elevated security?
#container#runtime#security#sandbox#kata
A
rune, cgroups
B
docker, containerd
C
runsc, kata
Correct
D
crun, cri-o
Resolution & Explanations
The correct answer is the group of container runtimes that provide additional sandboxed isolation and elevated security: runsc (gVisor) and kata (Kata Containers).
How it Works
Traditional container runtimes like runc and crun share the host kernel directly, offering limited isolation. In contrast, sandboxed runtimes introduce an additional layer of isolation:
runsc(gVisor): Implements a user-space kernel that intercepts system calls from the container, providing a security boundary without requiring hardware virtualization.kata(Kata Containers): Uses lightweight virtual machines (VMs) to run each container in its own dedicated kernel, leveraging hardware virtualization for strong isolation.
Why the Correct Value is Right
runsc and kata are explicitly designed for enhanced security through sandboxing. They are often used in multi-tenant environments where untrusted workloads must be isolated from the host and from each other.
Why the Incorrect Values are Wrong
runcandcgroups:runcis the standard OCI runtime that runs containers directly on the host kernel.cgroupsis a kernel feature for resource limiting, not a runtime. This combination does not provide sandboxed isolation.dockerandcontainerd: Docker is a container platform that usescontainerdas its runtime manager, which in turn usesruncby default. Neither provides additional sandboxing beyond standard container isolation.crunandcri-o:crunis a fast, low-level OCI runtime similar torunc.cri-ois a CRI-compliant container engine that typically usesruncorcrun. This combination lacks the extra isolation layer of sandboxed runtimes.