Deskpro instances run on Docker, and Docker requires an internal network to connect and communicate between containers.

By default, Docker will create the bridge network on the subnet 172.17.0.0/16

Additionally, Deskpro will create the deskpro_net network on the subnet 172.30.0.0/16 for the Deskpro instance containers.

There is a chance of network conflicts causing strange behaviours if you use these subnets within your LAN, so it is possible to change the subnets these services use to empty subnets to prevent conflicts.

Changing the Docker [bridge] network

As this is the default docker network, it is not possible to remove or modify it using CLI commands, and must be configured by modifying the daemon config.

Create the file /etc/docker/daemon.json with a text editor such as vi or nano, and paste the following:

{
  "default-address-pools": [
    {
      "base": "172.17.0.0/16",
      "size": 24
    }
  ]
}
 copy

You will need to change the base to the new subnet you would like to use. The size is the size of the pools within this subnet (in CIDR notation).

Once you've added that file, restart docker with systemctl restart docker

You should now be able to confirm the subnet has changed with the the following command:

docker network inspect bridge | grep Subnet
 copy

Changing the Deskpro [deskpro_net] network

The following OPC command will allow you to change the subnet used for the deskpro_net network:

opc config set docker-network --subnet <subnet>
 copy

You will need to replace <subnet> with the new subnet you would like to use in CIDR notation.

Once the OPC has completed its tasks, you can confirm the subnet has changed with the following command:

docker network inspect deskpro_net | grep Subnet
 copy