Fully autonomous AI Agents system capable of performing complex penetration testing tasks
Go ai-agentsai-security-toolanthropicautonomous-agentsgolanggptgraphqlmulti-agent-systemoffensive-securityopen-sourceopenaipenetration-testingpenetration-testing-toolsreactsecurity-automationsecurity-testingsecurity-toolsself-hosted
Merge branch 'feature/next-release' into codex/issue-69-openvas-custom-image-guide
Dmitry Ngfb607a8bc7dc
diff --cc README.mdindex a8e02c25,5714d768..7b248774--- a/README.md+++ b/README.md@@@ -2363,8 -2480,29 +2480,31 @@@ DOCKER_DEFAULT_IMAGE_FOR_PENTEST=mycomp> [!NOTE]> If a user explicitly specifies a particular Docker image in their task, the system will try to use that exact image, ignoring these settings. These variables only affect the system's automatic image selection process.+For an advanced OpenVAS/GVM experiment that uses a custom pentest image, see [OpenVAS via a Custom Pentest Image](examples/guides/openvas-custom-image.md).++ #### Restricted Networks, Docker Mirrors, and Proxies++ If your environment cannot reach Docker Hub (`docker.io`) directly, changing PentAGI environment variables is usually not enough to fix image download failures. PentAGI still relies on Docker's own registry access for Compose-managed services, and the installer network checks also validate Docker Hub reachability.++ For restricted networks:++ 1. Confirm that the host can resolve and reach `docker.io`.+ 2. If your environment requires an outbound proxy for PentAGI or installer HTTP traffic, set the `PROXY_URL` environment variable. To route Docker image pulls through a proxy, configure the Docker daemon or Docker Desktop proxy separately — Docker does not use PentAGI's `PROXY_URL` for registry access.+ 3. If Docker Hub is blocked or heavily rate-limited, configure an organization-approved registry mirror or registry proxy before running the installer or `docker compose up`.+ 4. Restart Docker after changing the daemon configuration, then rerun the installer checks or Compose startup.++ Example Docker daemon mirror configuration:++ ```json+ {+ "registry-mirrors": ["https://mirror.example.com"]+ }+ ```++ On Linux, this is typically configured in `/etc/docker/daemon.json`. On Docker Desktop, use the equivalent Docker Engine or proxy settings. A Docker Hub mirror covers Docker Hub-hosted images such as `vxcontrol/*`, but the main Compose stack already includes `quay.io/prometheuscommunity/postgres-exporter`, and the optional observability stack includes `gcr.io/cadvisor/cadvisor`. Those registries still need direct access or individually approved proxy/mirror paths.++ See the official Docker documentation for [registry mirrors](https://docs.docker.com/docker-hub/image-library/mirror/) and [daemon proxy configuration](https://docs.docker.com/engine/daemon/proxy/).+## Development### Development Requirements