From zero to a working Kali Linux shell with 100+ tools takes three commands and 30–45 minutes on a fresh Linux machine. After the one-time build, subsequent launches are instant. This guide walks you through the three-command setup, explains what you see on startup, and shows you how to connect to practice platforms like TryHackMe and HackTheBox from inside the container.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/V0rt3xS0urc3/RedTeam-Portfolio/llms.txt
Use this file to discover all available pages before exploring further.
Three-Command Quickstart
Run the Automated Installer
What You See on Launch
Every time the container starts,run-kali.sh prints a startup banner followed by a GPU detection message before handing you a shell:
/root/pentest and the following banner is displayed by .bashrc:
GPU Detection Output
After the banner,run-kali.sh automatically tests for an NVIDIA GPU and reports the result before starting the container:
With NVIDIA GPU and Container Toolkit configured:
Even without a GPU, all cracking tools function correctly — Hashcat simply runs on CPU. To enable GPU support after the fact, install the NVIDIA Container Toolkit on the host and run
sudo nvidia-ctk runtime configure --runtime=docker && sudo systemctl restart docker, then relaunch the container.Connecting to TryHackMe or HackTheBox
OpenVPN is pre-installed in the image. Download your.ovpn connection file from your platform’s dashboard and place it in the ./data/vpn/ directory on the host. That directory maps to /root/pentest/vpn/ inside the container.
Persistent Data Directory
All files you create or download inside the container at/root/pentest are automatically synced to the ./data/ directory on your host machine. Nothing is lost when the container exits.
| Container path | Host path | Purpose |
|---|---|---|
/root/pentest/wordlists/ | ./data/wordlists/ | Dictionaries (rockyou.txt, common.txt) |
/root/pentest/rules/ | ./data/rules/ | Hashcat rule files |
/root/pentest/handshakes/ | ./data/handshakes/ | Captured WiFi .pcapng / .hc22000 files |
/root/pentest/pcaps/ | ./data/pcaps/ | Raw packet capture files |
/root/pentest/loot/ | ./data/loot/ | Cracked credentials and results |
/root/pentest/vpn/ | ./data/vpn/ | OpenVPN .ovpn configuration files |
The
./scripts/ directory is also mounted into the container at /root/pentest/scripts as read-only. Helper scripts like auto-crack-wpa2.sh and setup-wifi.sh are available on $PATH inside the container.Next Steps
Run Modes
Deep-dive into
normal vs. wpa2 mode — what Docker flags each mode uses and when to choose one over the other.Tools Reference
Full catalogue of the 100+ tools included in the image, organized by category: recon, exploitation, web, AD, forensics, and more.
Auto-Crack WPA2
End-to-end walkthrough of the WPA2 cracking pipeline: monitor mode, handshake capture with
hcxdumptool, conversion, and GPU-accelerated Hashcat.