Containerized VSE not using the specified port range on docker run command line
search cancel

Containerized VSE not using the specified port range on docker run command line

book

Article ID: 222314

calendar_today

Updated On:

Products

Service Virtualization

Issue/Introduction

Have one VSE dockerized connecting to an on-prem Registry.  The VSE is running on it's own machine.

The VSE container is created with this command:

docker run -t -d --name VSEopenbanking --network="host" -p 9000-9100:9000-9100  -p 20112:20112 -p 1533:1533 -e LISA_MORE_VM_PROPS="-Diam.server.url=https://[server]:51111/auth" artifactory.[server]/docker-ca-sv-broadcom/sv/lisa:xx.x.0 VSE -m "tcp://[server]:2010/Registry" -n tcp://[server]:20112/VSEopenbanking

artifactory.[server]/docker-ca-sv-broadcom/sv/lisa:xx.x.0

We create a virtual service from RRpairs on the Portal.

The virtual service is created with a port number outside the 9000-9100 port range

where xx.x.o is the version of DevTest being run.

 

Environment

All supported DevTest releases.

Cause

N/A

Resolution

Add this on your docker command line -R 9000-9100

From our documentation:

By default, the VSE recording port numbers in the range 20000-20049 are exposed. You can change the range using the -R option.

For more information refer to section "DevTest with Docker Compose" in the documentation of the version of DevTest you are running.

After running the docker command you can create virtual service from the Portal for RRpairs and the port falls between the 9000 and 9100 range.