I couldn’t get the docker0 bridge to change, because I think that needs to be done by configuring DOCKER_OPTS before the docker engine itself starts up, and I couldn’t see anyway to hook into that. Luckily for us it was the “gwbridge” that conflicts.
This has gone somewhat off topic, but r.e. cloudstor I would like to be able to specify storage that is outside of the “docker-for-azure” resource group.
This is because if all data is stored outside the “docker-for-azure” resource group (i.e. databases, redis cache, file storage etc) it makes the resource group disposable. i.e. in a DR scenario, or if anything breaks (and I’ve broken it plenty in testing mainly by accidentally losing the raft quorum) then, it’s relatively easy to use version controlled templates and compose files to re-provision the entire stack and services in a new resource group, connect the services to the existing datastores, swap some DNS records, and delete the old resources. This could possibly even be done as a very safe way of doing blue/green swarm updates.
Not unlike having separate OS and data disks on a server, but on a slightly larger scale. The default could be like now, which is very easy to use, but just have some extra optional settings where needed. It would separate the “transient” data like OS disks etc from the business data.