-
Notifications
You must be signed in to change notification settings - Fork 0
Installation
Stephen edited this page Feb 27, 2026
·
2 revisions
| Requirement | Version | Purpose |
|---|---|---|
| Docker | 20.10+ | Container orchestration |
| Docker Compose | v2+ | Multi-service deployment |
| Go | 1.22+ | Build the CLI binary (or use pre-built release) |
| Python | 3.10+ | Orchestrator & dashboard (runs inside Docker) |
Test mode requires only Docker. Go is only needed if building from source.
Download from GitHub Releases:
chmod +x labyrinth
./labyrinth --install # Installs to ~/.local/bingit clone https://github.com/DaxxSec/labyrinth.git
cd labyrinth
./scripts/install.shThe install script will:
- Check for Go (install it if missing, with your permission)
- Build the CLI binary from source
- Install
labyrinthto~/.local/bin - Update your shell PATH
If you just want to deploy without the CLI binary:
git clone https://github.com/DaxxSec/labyrinth.git
cd labyrinth
./deploy.sh -tlabyrinth deploy -t # Deploy a test environmentThis will:
- Run preflight checks (Docker, ports, images)
- Build all Docker images
- Start the Docker Compose stack
- Register the environment in
~/.labyrinth/environments/
Your portal trap is now live:
| Service | Address | Purpose |
|---|---|---|
| SSH Portal Trap | localhost:2222 |
Point offensive agents here |
| HTTP Portal Trap | localhost:8080 |
Web-based attack surface |
| Web Dashboard | http://localhost:9000 |
Real-time web dashboard |
| TUI Dashboard | labyrinth tui |
Terminal monitoring dashboard |
Before your first real deployment, run the end-to-end smoke test. It builds the CLI, deploys the full stack, exercises every bait endpoint, verifies forensic capture, and tears down cleanly:
./scripts/smoke-test.shAll 22 checks should pass. If any fail, check the output — common issues are Docker not running or ports already in use.
After that, you can check environment status at any time:
labyrinth status # Check environment health
labyrinth list # List registered environments
labyrinth tui # Launch TUI monitoringlabyrinth teardown labyrinth-test # Tear down specific env
labyrinth teardown --all # Tear down everythingThe CLI binary can be removed from ~/.local/bin/labyrinth.
- CLI-Reference — All available commands
- Testing-with-Attackers — Set up an attacker agent
-
Configuration — Customize
labyrinth.yaml
Getting Started
Architecture
Layers
Operations