Page tree

Skip to end of metadata
Go to start of metadata

Jtest can be deployed in a Docker container to enable seamless integration with modern development workflows and CI/CD pipelines.

You can download a ready to use Jtest container image from Docker Hub: The container image includes Jtest and common utilities. See the documentation at Docker Hub for deployment and customization instructions.

Building a Custom Docker Container Image Locally


It is recommended to use Jtest container image from Docker Hub: Follow the steps below if you need to build a custom Docker container image, for example, if you have your own container base image.


  • Linux 64-bit
  • Docker
  • Jtest Standard installation package for Linux 64-bit

Building a Container Image

To build a Docker container image that includes Jtest:

  1. Review and modify the content of the <INSTALL_DIR>/integration/docker/Dockerfile to specify the tools you want to include in the container image.
  2. Optionally, configure Jtest before the container image is built. This allows you to provide a default Jtest configuration to all users of the image:
    • Open the '' file in the <INSTALL_DIR>/integration/docker directory.
    • Add the license settings and other configuration settings to the '' file.


      You must configure a network license to run Jtest in a Docker container. The local license is not supported. See Setting the License for details.

  3. Copy the Jtest distribution file (tar.gz) to the <INSTALL_DIR>/integration/docker/ directory.
  4. Run the following command in the <INSTALL_DIR>/integration/docker directory to build the image:

    docker build -t jtest:latest .

    The image will include runnable Jtest and other tools you specified in the Dockerfile.

  5. Once you built the Docker container image that includes Jtest, you can utilize all of Jtest's capabilities available from the command line interface:

    docker run --rm jtest:latest jtestcli -help

See the documentation at Docker Hub for further Jtest deployment and customization instructions:

See the documentation for Dockerfile:

  • No labels