This lesson teaches the concepts of container-based lab environments using the platform's built-in reference panel — no local installation required. You will inspect Docker concepts, command examples, Kali tool categories, and lab rules on the right. The page does not execute Docker or ask you to open a separate target.
This is a foundations lesson, not an exploitation walkthrough: the aim is a reliable, repeatable, and safe place to practice everything else in this course.
Scope reminder: this custom page is informational and executes no tools or target. In a real lab, test only systems you own or targets where you have explicit written authorization.
Two ideas anchor it:
- Isolation — a lab is valuable precisely because mistakes inside it cannot harm anyone or anything else.
- Authorization — the rule from
hacking-ethics-and-authorization: you test only systems you own or have explicit written permission to test. A controlled lab environment is the most direct way to honor that rule, because every target in it is yours.
In this lesson you will:
- See why a controlled, isolated lab is the right setting for intentionally destructive testing.
- Learn the difference between a virtual machine and a container, and between a Docker image and a container.
- Understand port mapping and read the single command that would run the bundled Nebula target in an authorized Docker environment.
- Meet Kali Linux, the conventional tool-laden attacker environment, and the idea of separating the attacker environment from the target environment.
- Reinforce the non-negotiable rule that your tools point only at owned or authorized targets.
Estimated time: ten to twelve minutes.
When you are ready, send the Continue signal.