A forensic tool for exploring offline Docker container filesystems and metadata from disk images.
Docker Explorer is a forensic analysis tool that allows investigators to explore offline Docker container filesystems and metadata from disk images. It solves the problem of analyzing compromised containers without requiring a live Docker environment, enabling forensic examination of container layers, configurations, and file contents directly from host storage.
Digital forensics analysts, incident responders, and security researchers who need to investigate Docker container compromises or analyze container artifacts in offline disk images.
Developers choose Docker Explorer because it provides accurate, offline access to Docker container filesystems using the same layered view as a running container, integrates with forensic workflows, and eliminates dependence on live Docker daemons during investigations.
A tool to help forensicate offline docker acquisitions
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Enables mounting and exploring Docker container filesystems directly from disk images without a live Docker daemon, as demonstrated in usage examples where it lists containers from /mnt/root/var/lib/docker.
Outputs structured JSON data compatible with tools like log2timeline, allowing seamless timeline analysis in forensic workflows, as noted in the key features.
Supports Docker storage drivers like AuFS and OverlayFS to accurately reconstruct container layers, essential for forensic examination of Docker's backend filesystems.
Extracts container metadata such as image history and configuration details from Docker's JSON files, providing insights without live access, as shown in the history command examples.
Requires installing packages like aufs-tools and specific Linux kernel modules, complicating setup, as highlighted in the troubleshooting section for mount errors.
Only works with Docker's storage formats; for Containerd systems, a separate tool (container-explorer) is needed, restricting its use in mixed environments.
The mount command can fail with errors related to filesystem types, requiring manual intervention and troubleshooting, as evidenced in the usage examples where additional apt commands are needed.