Disk Size for Docker Image

[Matt-Cross-1]

Quick question, possibly a good addition to the FAQ: How much disk space does the tool occupy, when the docker image is included? I'm just curious as to how much real estate this takes up, does it need to reside on a separate thumb drive from a bootable ISO for example... Many thanks for this impressive tool!

[cookesan]

The current default runtime image is adscan/adscan-lite:latest.

From the Docker manifest I get about 4.79 GB of compressed layers, roughly 4.46 GiB. Docker will also keep decompressed layer data, image metadata, pull cache, and ADscan workspaces, so the real disk budget should be higher than the pull size.

I would not put it on the same small boot ISO unless that environment has persistent Docker storage with several spare GB. As a practical floor, budget more than 10 GB for Docker's data root if you want room for the image plus outputs/logs; more if you plan to keep multiple versions or workspaces.

[Matt-Cross-1]

Awesome! Thank you for the excellent tool!

[ADScanPro]

Thanks @cookesan, that's a solid answer and the >10 GB budget is the right instinct. Let me add the exact numbers and clear up one distinction that trips people up, since it's worth getting right for the FAQ.

There are two different sizes:

• Pull size (compressed layers): ~4.8 GB, which is what you download. That's the number @cookesan quoted.
• On-disk size (decompressed): the current adscan/adscan-lite:latest unpacks to about 11.4 GB in Docker's data root. That's the number that answers "how much real estate does it take," since Docker stores the layers decompressed once pulled.

So for @Matt-Cross-1's actual question: budget around 15–20 GB free for Docker's data root. That covers the ~11.4 GB image plus room for your workspaces, logs, and any wordlists ADscan pulls, and a little headroom for a second version if you upgrade.

On the thumb-drive-next-to-a-bootable-ISO idea: it won't fit that way. ADscan runs inside Docker, so it needs a host with persistent Docker storage of that size, not a small removable volume shared with an ISO. A laptop or VM with ~20 GB free on the Docker data root is the right shape.

The image is large because it bundles the full offensive AD toolchain (Kerberos stack, the native protocol libraries, Chromium for report rendering, cracking tooling, and so on) so a scan needs no extra setup. Slimming it is on our radar, but correctness and "works out of the box" come first.

Good call that this belongs in the FAQ, will add it.