Share this page

# Manage Dockerized images

This section describes how to deploy Dockerized OpenText Enterprise Performance Engineering images and update the default image.

In this topic:

## 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:26.1 RHEL host: docker pull performancetesting/opentext_onelg_rhel:<tag version number> Example: docker pull performancetesting/opentext_onelg_rhel:26.1
Windows | docker pull performancetesting/opentext_onelg_windows:<tag version number> Example: docker pull performancetesting/opentext_onelg_windows:26.1

For details on deploying and running a Dockerized host, see Deploy Dockerized load generators on Windows and Deploy Dockerized load generators on Linux.

Back to top

## Deploy as a fully containerized environment

Note: This topic is relevant for testing purpose only.

You can perform a fully containerized deployment by installing the server, Controller, and load generator images on a Docker machine. You also need to deploy an image for your database: this must be provided by your database administrator.

You can pull the 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
--- | ---
Server | docker pull performancetesting/lreserver:<tag version number> Example: docker pull performancetesting/lreserver:26.1
Controller (data processor) | docker pull performancetesting/host:<tag version number> Example: docker pull performancetesting/host:26.1 Note: You cannot use 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 fully containerized environment, see Fully containerized environment.

Back to top

Next steps:

- Provision Docker hosts automatically
- Provision Docker hosts manually
- Fully containerized environment

https://admhelp.microfocus.com Enterprise Performance Engineering,LoadRunner Enterprise 8942
Tips to improve your search results...OpenText™ Enterprise Performance Engineering Help Center OpenText™ Enterprise Performance Engineering Help 26.1 All View Local Help Center View Online Help Center Version: