Page tree
Skip to end of metadata
Go to start of metadata

Draft

This page is a draft and may contain incomplete or inaccurate information

This is a draft and not a recommendation

Background

In testing, one ITC had a conflict with the IP addresses assigned automatically by Docker.  They tried to adjust the default docker bridge network but that did not resolve the issue. Per this article, IP ranges can be adjusted in the docker-compose.override file. Examples follow.

Standard docker-compose.override file (network section) and results from inspecting the network created:

networks:
   proxy:
     external:
        name: proxy_default

docker inspect test_default (that was the name of the network created)shows this in the IPAM section:
 "IPAM": {
            "Driver": "default",
            "Options": null,
            "Config": [
                {
                    "Subnet": "172.19.0.0/16",
                    "Gateway": "172.19.0.1"
                }
            ]
        },

Modified docker-compose.override.yml file (network section) and results from inspecting the network created:

networks:
   proxy:
     external:
        name: proxy_default
   default:
     ipam:
       driver: default
       config:
       -
          subnet: 172.16.238.0/24


docker inspect test_default (that was the name of the network created)  showed this in the IPAM section:
 "IPAM": {
            "Driver": "default",
            "Options": null,
            "Config": [
                {
                    "Subnet": "172.16.238.0/24"
                }
            ]
        },


This is an example of the network section of the docker-compose file for the ITC with the conflict.  They plan to increment the third octet of the IP address in each one.  So, for the "- subnet:" on the next instance, they will use 172.30.1.0/24, then 172.30.2.0/24, etc.

Version: "3.3"

networks:
   proxy:
     external:
        name: proxy_default
   default:
     ipam:
        driver: default
        config:
          - subnet: 172.30.0.0/24