The docker-compose.yaml file provided should not be modified. This is to ensure that we can support our customers’ server deployments and ensure that all servers are deployed in a consistent manner.
In addition, should these files require an update in the future, modifications could prove problematic if the files have been customized by the end user.
The docker-compose files are kept as generic as possible to avoid any conflicts with our customers deployment environments.
If you would like to make changes to the docker-compose file, please make use of Dockers multiple compose file option. This option will allow you to customize the configuration used to run your servers, without modifying the original files that we provide.
Example: Customizing the default network
A common change that you may want to make is to customize the subnet used by the default network. We should be able to make this change by adding the following to the end of the docker-compose (e.g. docker-compose.yaml) file:
networks:
default:
ipam:
driver: default
config:
- subnet: 172.33.0.0/16We would like to make this change to the deployment of our Standard Transform Add-on (CTAS) server, but without editing the docker-compose.yaml file. We can create a new docker-compose file that will contain our custom deployment options for the server. We will create a new file called “ctas-custom.yaml” with the following contents:
version: "3"
networks:
default:
ipam:
config:
- subnet: 192.0.2.0/24We can now run our server using a combination of the two configurations files, with the following command:
docker compose -f docker-compose.yaml -f ctas-custom.yaml up