In some place, the host main network is on subnet 172.16.0.0 which is the one used by docker.
If the docker network is not updated it can cause some trouble when you try to access servers outside of the host and on the subnet 172.16.0.0.
The solution is to create/update /etc/docker/daemon.json and define as follow :
{
"bip": "{anotherSubnett}/16"
}Then you need to restart docker and then the subnet is updated.
Therefore, it is recommended to do it before launching any container (with or without docker-compose) otherwise, you will need to manually recreate every network (by adding --recreate to docker-compose up for example)
In some place, the host main network is on subnet 172.16.0.0 which is the one used by docker.
If the docker network is not updated it can cause some trouble when you try to access servers outside of the host and on the subnet 172.16.0.0.
The solution is to create/update /etc/docker/daemon.json and define as follow :
{ "bip": "{anotherSubnett}/16" }Then you need to restart docker and then the subnet is updated.
Therefore, it is recommended to do it before launching any container (with or without docker-compose) otherwise, you will need to manually recreate every network (by adding --recreate to docker-compose up for example)