Hardening Docker Containers Using gVisor Runtime
Configure Docker to use gVisor (runsc) as the default runtime and verify kernel isolation between the host and containers.
Focused, hands-on problems for sharpening your DevOps and server-side skills. Some teach specific concepts while others mirror real-world scenarios. Every challenge includes hints, feedback, and automated solution checks.
Configure Docker to use gVisor (runsc) as the default runtime and verify kernel isolation between the host and containers.
In this challenge, you will practice installing and configuring containerd: obtaining the release binaries, placing them in the correct locations, adding the container runtime and CNI plugins to the system, and starting a container with full networking support.
Can you unpack the filesystem of a container image into a local directory?
Can you start a container using the default containerd CLI, ctr? Knowing how to use ctr may come in handy when you need to debug lower-level container issues.
Learn a trick or two about container image labels and how to read them with ctr.
Can you find a way to execute a command in a Docker container using ctr?