Problem: A Docker App Uses a Network Range Which Is Used Locally

[Christian_Voelker]

Problem:

A Docker app uses a network range which is already used in the local network (LAN). Therefore your app can not be reached through network.

Solution

Switch the docker network to a different network. There might be two docker networks. You can move both or only the disturbing one, but they must be different:
ucr set appcenter/docker/compose/network="172.31.0.1/16"
ucr set docker/daemon/default/opts/bip="172.33.0.1/16"
If you change the docker/daemon/default/opts/bip you need to restart the docker daemon:
systemctl restart docker.service

Note: You should not use assigned networks. Use a network from within the available ranges for private networks as written in RFC1928

How-to: Docker in UCS - change the default docker subnet IP range with UCRV

How to: If it is necessary that you want to change the IP range for the docker itself in UCS but also the docker container installation for apps from the Appcenter, this is possible by adjusting existing UCR variables. Here are the UCR variables required for this: appcenter/docker/compose/network appcenter/docker/compose/network: 192.168.1.1/16 Network, in which Docker Compose based Apps are installed (will be used on next installation / upgrade). Every App gets its own subnet, so choose a …