The itds.yml and ctas.yml files provided should not be modified. This ensures that we are able support our customers server deployments, and that all servers are deployed in a consistent manner. We may need to update these files in the future, which will be problematic if the files have been customised 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 customise the configuration used to run your servers, without modifying the original files that we provide.


Example: Customising the default network

A common change that you may want to make is customise 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. ctas.yml) file:


networks:
 default:
  ipam:
   driver: default
   config:
   - subnet: 172.33.0.0/16


We would like to make this change to the deployment of our CTAS server, but without editing the ctas.yml 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.yml" with the following contents:


version: "3"
networks:
  default:
    ipam:
      config:
        - subnet: 192.0.2.0/24


We can now run our server using a combination of the two configurations files, with the following command:


docker-compose -f ctas.yml -f ctas-custom.yml up