Mastering Redamon: A Comprehensive Guide to Installation on Kali Linux

Overcoming BuildKit Networking, Image Tagging, and Docker Compose Hurdles

The Redamon framework is a powerful asset for security professionals, but deploying it on Kali Linux often presents unique challenges. Due to Kali’s strict security posture, Docker BuildKit frequently runs into networking restrictions or fails to correctly “tag” images after a successful build.

This guide provides a step-by-step roadmap to navigate these technical roadblocks and get your environment up and running.

1. Environment Preparation

In modern Kali Linux distributions, the old Docker Compose V1 (docker-compose with a hyphen) is deprecated. You must use the Docker Compose V2 syntax, which uses a space: docker compose.

Ensure you are in the project’s root directory:

Bash

cd ~/redamon

2. Solving the Network Privilege Issue

During the build process, Docker may request specific privileges to access the host network, which is essential for Kali to download necessary security packages. Standard build commands often fail because these privileges are not granted by default.

The Buildx Bake Solution

To build all images simultaneously while explicitly granting the required network permissions, use the bake command with the following flags:

Bash

sudo docker buildx bake \
  --allow=network.host \
  --allow=fs.read=/home/kali/redamon \
  --load

• **--allow=network.host**: Explicitly grants the container network access to download dependencies.
• **--load**: Ensures the resulting images are moved from the build cache into your local Docker image library (docker images).

3. Manual Image Registration

If the automated build fails to label your images correctly — particularly the kali-sandbox due to sub-directory structures—you must register them manually.

Manual Build for Kali-Sandbox

The kali-sandbox service often resides within a sub-folder (e.g., /mcp). If Docker Compose reports a "No such image" error, trigger the build by pointing to the correct context:

Bash

sudo docker build --network=host -t redamon-kali-sandbox:latest -f ./mcp/kali-sandbox/Dockerfile ./mcp

Manual Build for the Webapp

Bash

sudo docker build --network=host -t redamon-webapp:latest ./webapp

4. Validating the “Image Gallery”

Before attempting to launch the system, verify that all five fundamental components are present in your local registry:

Bash

sudo docker images | grep redamon

Your list must include:

• redamon-agent
• redamon-recon-orchestrator
• redamon-webapp
• redamon-kali-sandbox
• redamon-recon

5. System Initialization

With your images verified, launch the services using the “tools” profile. We use the --no-build flag to prevent Docker from attempting to re-run the faulty automated build process:

Bash

sudo docker compose --profile tools up -d --no-build

Accessing the Dashboard

Once the containers are “Started” and the database volumes (postgres and neo4j) are initialized, Redamon will be accessible at: [**http://localhost:3000](http://localhost:3000)**

Pro-Tips for Troubleshooting

• Command Not Found: Always double-check that you are using docker compose (space) and not docker-compose (hyphen).
• Orphaned Images: If you see images listed as <none> after a build, identify the Image ID and manually tag it: sudo docker tag [ID] redamon-kali-sandbox:latest.
• Monitoring: Use sudo docker compose logs -f to watch the real-time startup of the agent and orchestrator to ensure they connect to the database correctly.