API Gateway 10.11 | Administering API Gateway | Container-based Provisioning | Docker Configuration | Running the API Gateway Container
 
Running the API Gateway Container
Before starting API Gateway, ensure that the main memory and the kernel settings of your docker host are correctly configured. The docker host should provide at least 4 GB of main memory. Since API Gateway comes with an Elasticsearch, the vm.max_map_count kernel setting needs to be set to at least 262144. You can change the setting on your docker host by running the following command:
sysctl -w vm.max_map_count=262144
For further details about the important system settings to be considered, see the Elasticsearch documentation.
* Start the API Gateway image using the docker run command:
docker run -d -p 5555:5555 -p 9072:9072 -name apigw is:apigw
The docker run is parameterized with the IS and the webApp port exposed by the Docker container. If you have configured different ports for IS and UI, the call has to be adapted accordingly. The name of the container is set to apigw.
The status of the Docker container can be determined by running the docker ps command: docker ps
A sample output looks as follows:

CONTAINER ID IMAGE COMMAND CREATED STATUS ->
5b95c9badd59 is:apigw "/bin/sh -c 'cd /s..." 15 hours ago Up 15 hours
->
PORTS NAMES
0.0.0.0:5555->5555/tcp, 0.0.0.0:9072->9072/tcp, 9999/tcp apigw