You need to create a
deployment-config.toml file and use it as the input to the WSO2 API Microgateway Toolkit in order to create a Docker image by including the runtime executable artifacts, so that you do not have to mount the artifacts from outside. When using this approach, it will generate the Docker images from the WSO2 API Microgateway base image by including all the API runtime artifacts as well.
The following is a sample
Descriptions for the configurations
Name of the Docker image.
Note that the Docker image name must be specified in lower case.
|Name of the Docker registry.||None|
|The Docker image tag.||latest|
|Enable or disable the option to build the Docker images.||true|
|Docker host IP and Docker PORT. (e.g., minikube IP and Docker PORT)||unix:///var/run/docker.sock|
|Docker cert path.||null|
|Base image to create the Docker image.||ballerina/ballerina:latest|
|Enable or disable debugging.||false|
|Remote debug port.||5005|
|Enable or disable pushing the Docker image to the remote registry.||false|
|Username for Docker registry.||None|
|Password for Docker registry.||None|
|The source path of the file (in your local machine).||None|
|The target path (inside the container).||None|
|This option indicates whether the file is a Ballerina config file or not.||false|
The following code snippet, which is present in the above sample code, is used to enable the Docker copy files configuration in order to copy the
micro-gw.conf file to the Docker image as it contains the Key Manager configurations, JWT configurations, etc.