Integration Server 10.3 | Microservices Runtime Guide | Using Configuration Variables Templates with Microservices Runtime | Providing a Configuration Variables Template when Starting a Docker Container
 
Providing a Configuration Variables Template when Starting a Docker Container
When running a Microservices Runtime image in a Docker container, you can specify the configuration variables template and/or environment (ENV) variables in the docker run command.
Example
The following docker run command uses the SAG_IS_CONFIG_PROPERTIES ENV variable to specify the name and location of the configuration variables template. In this example, the Docker image for the Microservices Runtime is named is:microPkg and exposes ports 5555 and 9999. Additionally, the customApplication.properties file location is accessible by the Docker container using Docker volume.
docker run -d --name IS_Default -p 5555 -p 9999
-v /opt/softwareag/customApplication.properties:/opt/softwareag/customApplication.properties
-e SAG_IS_CONFIG_PROPERTIES=/opt/softwareag/customApplication.properties
is:microPkg
Example
The following docker run command uses the SAG_IS_CONFIG_PROPERTIES ENV variable to specify the name and location of the configuration variables template and uses the --env-file option to specify the list of ENV variables that are used in the configuration variables template. In this example, the Docker image for the Microservices Runtime is named is:microPkg and exposes ports 5555 and 9999.
docker run -d --name IS_Default -p 5555 -p 9999
-e SAG_IS_CONFIG_PROPERTIES=/opt/softwareag/customApplication.properties
-v /opt/softwareag/customApplication.properties:/opt/softwareag/customApplication.properties
--env-file env.list is:microPkg