Manage Dockerized images

This section describes how to deploy Dockerized LoadRunner Enterprise images and update the default image.

Deploy Dockerized load generator images

Dockerized load generator images are available in the Docker repository.

You can pull the image from the from the relevant page, accessible from the performance testing page (https://hub.docker.com/u/performancetesting) in the Docker hub, using the commands below.

Environment Command

Linux

Two images are available, Linux-Ubuntu and RHEL.

  • Ubuntu host:

    docker pull performancetesting/opentext_onelg_ubuntu:<tag version number>

    Example: docker pull performancetesting/opentext_onelg_ubuntu:24.1

  • RHEL host:

    docker pull performancetesting/opentext_onelg_rhel:<tag version number>

    Example: docker pull performancetesting/opentext_onelg_rhel:24.1

Windows

docker pull performancetesting/opentext_onelg_windows:<tag version number>

Example: docker pull performancetesting/opentext_onelg_windows:24.1

For details on deploying and running a Dockerized host, see the LoadRunner Enterprise Installation Guide (available from Installation).

Back to top

Deploy LoadRunner Enterprise as a fully containerized environment

Note: This topic is relevant for testing purpose only.

You can perform a fully containerized LoadRunner Enterprise deployment by installing the LoadRunner Enterprise Server, Controller, and load generator images on a Docker machine. In addition, you need to deploy an image for your database (this must be provided by your database administrator).

You can pull the LoadRunner Enterprise Server, Controller, and load generator images from the https://hub.docker.com/r/performancetesting/ page in the Docker hub, using the following commands:

Image Command
LoadRunner Enterprise Server

docker pull performancetesting/lreserver:<tag version number>

Example: docker pull performancetesting/lreserver:24.1
Controller (data processor)

docker pull performancetesting/host:<tag version number>

Example: docker pull performancetesting/host:24.1

Note: You cannot utilize a Controller image as a load generator due to a port conflict with the load generator image, which results in the load generator ports for the Controller image being closed.

Load Generator

See Deploy Dockerized load generator images above.

For details on setting up a LoadRunner Enterprise fully containerized environment, see Fully containerized environment.

Back to top

Next steps: