The native scheduler creates an additional bridge network for the audit log containers named replicated_retraced. On most servers the default bridge network will be assigned the subnet 172.17.0.0/16 and the replicated_retraced bridge network will receive 172.18.0.0/16. In other cases where docker is configured to use an alternative subnet, the replicated_retraced network should be pre-created:
docker network create replicated_retraced --subnet=172.20.0.0/24
If you need to delete the replicated_retraced network so you can create it with a different subnet, use these commands:
systemctl stop replicated
docker rm -f retraced-api retraced-cron retraced-postgres retraced-nsqd retraced-processor
docker network rm replicated_retraced
docker network create replicated_retraced --subnet=172.20.0.0/24
systemctl start replicated
If you want to check which subnet the network is using:
docker network inspect replicated_retraced
If it happens to be the case that the main docker bridge IP range is also not acceptable, it is changed with a different procedure:
If Replicated has not yet been installed, you can simply set the bridge IP range in /etc/docker/daemon.json like so:
{
"bip": "1.2.3.0/24"
}
with your preferred IP range, and then restart docker.
If Replicated was previously installed, then you will need to edit the bridge IP as above, and then update the IP addresses present within /etc/default/replicated and /etc/default/replicated-operator, replacing 192.17.0.1.