Challenge, Medium,  on  Containers

Hardening Docker Containers Using gVisor Runtime

Scenario

You are responsible for hardening Docker workloads on a system that requires strong container isolation.

The environment already includes gVisor (runsc).

Tasks

  1. Your task is to configure Docker so that all new containers use gVisor as the default runtime.
  2. Start a container and record:
    • the container kernel release in:
     /root/container-kerneal-release.txt
  • the host kernel release in:
     /root/host-kerneal-release.txt
  1. Ensure that the kernel releases in both files are different.

🧪 Test Cases

Level up your Server Side game — Join 20,000 engineers who receive insightful learning materials straight to their inbox

How to Author Challenges on iximiuz Labs

Instead of providing a subpar online editing experience, iximiuz Labs offers a helper CLI tool called labctl, allowing you to use your favorite text editor (or a full-featured IDE) to write content from the comfort of your local machine.

Install labctl CLI

curl -sf https://labs.iximiuz.com/cli/install.sh | sh

This will download and install the latest version of the labctl CLI. You only need to do this once per workstation.

Authorize labctl

labctl auth login

This will open a browser window asking you to authorize labctl to access your account. You need to do it after a fresh install of labctl and repeat it whenever the auth session expires.

Pull challenge content

labctl content pull challenge hardening-docker-containers-using-gVisor-runtime-c057e247

This will create a local copy of the challenge content in a directory named hardening-docker-containers-using-gVisor-runtime-c057e247. You only need to do this once per challenge.

Stream your changes

labctl content push -fw challenge hardening-docker-containers-using-gVisor-runtime-c057e247

Run this command in a separate terminal to continuously upload your changes to the server while editing the challenge in your favorite text editor or IDE.

You can also use labctl to create, list, and delete your content. Learn more about the available commands: labctl content --help

Start challenge