Security Tests in Docker

Applies to ReadyAPI 3.40.1, last modified on June 29, 2022


Docker runs applications in light-weight virtual containers. The containers provide you with a consistent environment isolated from other applications. SmartBear provides you with the readyapi-security-testrunner docker image you can use to run ReadyAPI security tests within containers. The image is available in Docker Hub.

Docker image

To run security tests in Docker, use the following image from Docker Hub:

Required license

To use the image, you must have a file-based Floating license. When you run a container, it connects to the specified license server and obtains the license. The license server must be available to the container and must be properly configured. See Configure License Server 5.x.

Hardware requirements

This topic describes how to use Docker with ReadyAPI on the Hyper-V virtualization platform. To do that, use the same environment you use to run your Docker images. There are no specific requirements for this.

To learn more, see the Docker documentation:

To run ReadyAPI tools in Docker containers on other virtualization platforms, additional configuration may be required. Please see the corresponding documentation.

Known issue: You cannot run the readyapi-security-testrunner image by using the Docker toolbox.

Pulling Security Test Runner image from Docker Hub

To run functional tests by using a Docker image, you need to pull it from Docker Hub. To do this, use the following command:

docker pull smartbear/readyapi-security-testrunner

Docker command syntax

To run a functional test in a Docker container, use the following command line:

docker run -v="Project Folder":/project -v="Report Folder":/reports -v="Extensions Folder":/ext -e LICENSE_SERVER="License Server Address" -e COMMAND_LINE="Test Runner Arguments" -it smartbear/readyapi-security-testrunner:latest


-v=Project Folder:/project

Required. Specifies the path to the folder that contains the ReadyAPI project. When a container starts, this folder will be copied to the container.
Usage: -v="C:\Work\ReadyAPI Project":/project
Note: On some systems, you may need to change the path in the following way:
"C:\Work\ReadyAPI Project" -> "/host_mnt/C/Work/ReadyAPI Project"

-v=Report Folder:/reports

Specifies the folder on a local machine to which the generated reports will be exported.
Usage: -v="C:\Work\Reports":/reports
Note: On some systems, you may need to change the path in the following way:
"C:\Work\Reports" -> "/host_mnt/C/Work/Reports"

-v=Extensions Folder:/ext

Specifies the folder whose content should be copied to the /bin/ext folder of the ReadyAPI installation in the container. Use this argument if your project requires additional libraries, such as database drivers or plugins.

Usage: -v="C:\Work\ReadyAPI Extensions":/ext
Note: On some systems, you may need to change the path in the following way:
"C:\Work\ReadyAPI Extensions" -> "/host_mnt/C/Work/ReadyAPI Extensions"

-v=Plugins Folder:/root/.soapui/plugins

Specifies the folder with plugins that should be installed to ReadyAPI in the container.

Usage: -v="C:\Users\<User>\.soapui\plugins":/root/.soapui/plugins
Note: On some systems, you may need to change the path in the following way:
"C:\Users\<User>\.soapui\plugins" -> "/host_mnt/C/Users/<User>/.soapui/plugins"

-e LICENSE_SERVER="License Server Address"

Required. Specifies the address of the license server. When a container runs, it connects to the specified server to obtain a Floating ReadyAPI Test license.
Make sure the container is able to connect to the license server using the IP you specify, regardless of whether you use a public or private IP address.


-e COMMAND_LINE="Test Runner Arguments"

Required. Specifies arguments for the test runner. The %project% variable refers to the container folder to which the contents of the project folder were copied. To refer to the reports volume, use the %reports% variable.


-e COMMAND_LINE="-f/%reports% '-RSecurity Issues Report' -FPDF '-EDefault environment' -nSecurityTest1 '/%project%/Sample-readyapi-project.xml'"


Required. This command enables the interactive command-line interface within a Docker container.


Required. Specifies the image to create a container from.

Sample full command

docker run -v="C:\Tests\Project":/project -v="C:\Tests\Reports":/reports -v="C:\Tests\Extensions":/ext -e LICENSE_SERVER="" -e COMMAND_LINE="-f/%reports% '-RSecurity Issues Report' -FPDF '-EDefault environment' -nSecurityTest1 '/%project%/Sample-readyapi-project.xml'" -it smartbear/readyapi-security-testrunner:latest

Exit codes

After the docker stops running, you can get the exit code by using the following command:

PowerShell (Windows)

Command Prompt (Windows)

Terminal (macOS and Linux)

Besides the standard Docker exit codes (see the Docker documentation) the readyapi-security-testrunner Docker image uses the following codes:

101 Contained ReadyAPI cannot start due to a license issue.
Make sure the license server is properly configured and the Docker image can access to it. See other possible issues with Floating licenses.
102 The ReadyAPI project was not found.
Make sure you specify the correct folder for the project volume, and this folder contains the specified project.
103 An error occurs during the test run. See the test log for more details.

If you cannot run Docker due to the Drive has not been shared error, perform the following steps:

  1. Right-click the Docker icon in the notification area and select Settings:

    Docker image: Docker context menu
  2. On the Shared Drives page of the Settings dialog, select all the drives you use to run the Docker container.

    If your drives have already been shared, but the error occurs anyway, turn off sharing. After you apply the changes, repeat these steps to share the drives again.

    To share your drivers, select them in the list and click Apply:

    Docker image: Docker context menu

    Click the image to enlarge it.

    You may need to enter the credentials of your system account to apply the changes.

See Also

Docker Images
Configure License Server 5.x
Functional Tests in Docker
Run TestEngine in Docker Container
VirtServer in Docker
LoadUI agent for Docker

Highlight search results