Supported platforms, privileges, and networking expectations before running ADscan.

ADscan is Linux-first. Use this checklist to make sure your jump box, lab VM, or CI runner matches what the installer expects.

Supported platforms

Component	Requirement
Operating system	64-bit Linux (x86_64/amd64) with Docker support (CI-verified on the versions listed below).
Docker	Docker Engine (`docker`).
Privileges	Ability to run Docker (root or in the `docker` group).
Python	3.8+ (only used for the launcher; ADscan runs in a container by default).
Storage	≥15 GB free (ADscan container image + workspace data + Docker layers).
Memory / CPU	Minimum 4 GB RAM / 2 vCPU. Recommended 8 GB RAM / 4 vCPU for large engagements.
Network	Internet access for image pulls and Layer 3/4 reachability to the target AD environment.

ADscan is tested continuously on:

macOS (launcher runtime commands are Linux-only)
Windows (native launcher runtime commands are Linux-only)
WSL / WSL2 (Docker-mode launcher runtime is blocked by default; use a native Linux VM/host)
Linux arm64 / aarch64 (including Apple Silicon Linux hosts/VMs) for Docker-mode runtime commands
Kali Linux ≤ 2024.2 (older baselines often cause issues; not recommended)
Arch-based distributions (Arch, Manjaro, Garuda, etc.)
RPM-based distributions (Fedora, RHEL, CentOS, Rocky/AlmaLinux, etc.)

Recommended baseline: Kali Linux 2025.4 or Ubuntu 24.04 LTS, 30 GB of disk, and Docker installed.

What gets stored where?

Workspaces live under ~/.adscan/workspaces (host).
Docker images are stored under Docker’s storage directory (commonly /var/lib/docker).
Attack-path graphs (BloodHound-compatible JSON) are written inside each workspace under domains/<domain>/attack_graph.json. To explore them visually, point your own BloodHound CE instance at that file.

# Verify launcher version and dependency health
adscan --version
adscan check

# Confirm Docker availability
docker info

The legacy host-based installer exists for environments where Docker is not allowed:

adscan install --legacy
adscan check --legacy --fix

Legacy mode requires many more host dependencies (apt, Python toolchains, Go/Rust, etc.) and is not recommended unless you must.

Keep enough free disk and back up before rotating runners.
Allow outbound SMB/LDAP/RPC to the target domain plus HTTPS to container registries and release mirrors.

Meeting these baselines prevents surprise installer failures and unlocks the full ADscan LITE/PRO workflow.