Share this page

# Docker installation

This section describes how to install OpenText Functional Testing Lab on a Linux platform using Docker. With Docker, you develop, ship, and run applications using a container.

This section is not relevant for OpenText Core SDP and OpenText Core Functional Testing Lab.

In this topic:

## Overview

Docker uses a standard container format that lets developers prepare applications inside containers. System administrators and other teams, such as Quality Assurance engineers, run the container to deploy the application. For details, see the Docker documentation.

Back to top

## Install Docker

Docker uses a standard container format that lets developers prepare applications inside containers. System administrators and other teams, such as Quality Assurance engineers, run the container to deploy the application. For details, see the Docker documentation.

Follow the steps below to install Docker:

1. Install Docker on the target machine, along with its dependencies. Currently, only the 64-bit version is supported. For installation details, see the Docker Installation guide.
2. Set up the target machine environment as required.

Back to top

## Obtain the server image

Obtain the latest OpenText Functional Testing Lab Docker image from the Docker hub.

At the command prompt, type the following in your Linux environment:

Copy code

    docker pull mobilelifecycle/uft-digitallab:2025.2.0

The image contains the Dockerfile of the OpenText Functional Testing Lab server that connects to a remote Postgres database. (The database installation is not included in the package.)

Note that SSL is not supported when installing OpenText Functional Testing Lab with a Docker image.

Back to top

## Run PostgreSQL

The PostgreSQL database used by the lab is not included in the OpenText Functional Testing Lab server image. Make sure that you have the PostgreSQL database up and running on a machine that can be accessed by the server.

We recommend PostgreSQL version 11. If you don't have PostgreSQL, obtain it from the Docker hub by typing `docker pull postgres:11`.

To run the PostgreSQL container in the background:

Enter the following command when using the default PostgreSQL port (5432):

Copy code

    docker run --name postgres -p 5432:5432 -e POSTGRES_PASSWORD=[postgres_password] -d postgres:[PostgreSQL version number]

If you need to use a custom port, run the following:

Copy code

    docker run --name postgres -p [custom_port]:5432 -e POSTGRES_PASSWORD=[postgres_password] -d postgres:[PostgreSQL version number]

Make sure to use this custom port for POSTGRES_PORT= in the command for running the server in Start a container and launch the server.

Note: PostgreSQL adds a default user postgres.

Back to top

## Start a container and launch the server

After you have the PostgreSQL database up and running, start the OpenText Functional Testing Lab server container.

To start the container:

1. Check that the default port, 8080, is available and not being used by another process.

2. Run the following command to run the server in the background in detached mode. The default PostgreSQL user is postgres:

   Copy code

       docker run -d --name ftlab -p 8080:8080 -e POSTGRES_HOST=[postgres_ip] -e POSTGRES_PORT=5432 -e POSTGRES_USER=[postgres_user] -e POSTGRES_PASSWORD=[postgres_password] -e FQDN=[host_ip] mobilelifecycle/uft-digitallab

   If you need to use a custom port, specify the custom port as follows:

   Copy code

       docker run -d --name ftlab -p [custom_port]:8080 -e POSTGRES_HOST=[postgres_ip] -e POSTGRES_PORT=5432 -e POSTGRES_USER=[postgres_user] -e POSTGRES_PASSWORD=[postgres_password] -e FQDN=127.0.0.1 -e EXTERNAL_PORT=<custom_port> mobilelifecycle/uft-digitallab

   Note:

   - When using a custom port, set FQDN to 127.0.0.1

   - If you specify non-default ports, you also need to modify the ports on the connector and tools.

Applications are stored on the physical disk. This means you need to use a volume to maintain the persistence of the applications after the container is exited:

Copy code

    docker volume create ftlab_data
    docker run -d --name ftlab [options] -v ftlab_data:/opt/FunctionalTestingForMobileAndWeb/mcStorage mobilelifecycle/uft-digitallab

Back to top

## Begin your test

To use OpenText Functional Testing Lab for testing your mobile app:

1. Open the OpenText Functional Testing Lab home page http://<host>:<port> and log in with the default credentials:
   Email: admin@default.com
   Password: password
   It may take a minute for the server to start up, and for the page to open.
2. Install a connector on the machine/s to which you are connecting devices with a USB cable. You can connect multiple devices to the Docker host machine. The connector can be installed on the same machine on which Docker is installed. For details, see Install the connector on a Windows machine, Install the connector on a Linux machine or Install the connector on a Mac machine.

3. Prepare your OpenText Functional Testing Lab test with the relevant testing tool.

Back to top

## Tips and guidelines

The following table includes a list of useful Docker commands:

Command | Action
--- | ---
`docker ps` | Lists the containers that are running
`docker stop ftlab` | Stops the lab service
`docker start ftlab` | Starts the lab service
`docker images` | Lists the images
`docker inspect ftlab|grep '"Source": "/var/lib/docker/volumes'` | Check the logs of the running OpenText Functional Testing Lab container. The output has the following form: `"Source": "/var/lib/docker/volumes/07ec0041ecf5f86934d2957648a24248fefeffdbb0da3a5b353d1d1fe480b656/_data"` Append server/log to the above path shown in the output. This folder contains the log files.

Back to top

See also:

- Get started
- Lab console

https://admhelp.microfocus.com/Functional Testing Lab 8942
Tips to improve your search results... OpenText™ Functional Testing Lab for Mobile and Web Help Center OpenText™ Functional Testing Lab Help 25.2 All View Local Help Center View Online Help Center Version: