Skip to main content
The Docker agent is a containerized VPN agent for environments already running Docker. It works on Linux, Windows, and macOS (including Apple Silicon).
VPN profiles require the Internal network scanning add-on.

Prerequisites

  • Docker installed and running
  • Outbound connectivity to vpn2.pentest-tools.com on TCP port 22
  • Network access to internal targets from the Docker host

Quick start

1

Create VPN profile

In Pentest-Tools.com, create a new VPN profile and copy the VPN UUID.
2

Pull and run

Run the following command, replacing <VPN_UUID> with your UUID:
You can also copy this command directly from the deployment menu in Settings > VPN Profiles.
3

Verify connection

Go to Settings > VPN Profiles and check that your profile shows as Online.

Required capabilities

The agent needs these Linux capabilities:

Network modes

By default, the container uses Docker’s bridge network. Depending on your setup, you may need a different mode.

Host network mode

Gives the container direct access to the host’s network interfaces:
Host network mode exposes the container’s ports directly on the host machine. This can cause conflicts if ports 80, 443, or 1194 are already in use on the host. It also means the agent’s network traffic is not isolated from the host.

Custom Docker network

To scan containers in a specific Docker network:

Docker Compose

Set your VPN UUID as the command in the Compose file:
Replace <VPN_UUID> with the UUID from your VPN profile.
Start the agent in the background:

Managing the agent

Troubleshooting

  • Check that the VPN UUID is provided as an argument after the image name
  • Verify --cap-add=NET_ADMIN is set
  • Check that the /dev/net/tun device is mounted
  • Check container logs: docker logs pentest-agent
  • Verify the container’s network mode allows access to targets
  • Check host firewall rules
  • Try --network host mode