Blacklist IP Ranges for docker-compose

At our company we use several IP ranges for server deployments. Docker-compose, after some time, begins to conflict with these machines. Therefor I have the following question:
Can you force docker-compose/docker NOT to create networks in certain IP ranges?

He there,

I think I answered that in another thread.

just look at the part how to change the ip of the docker bridge

hope that helps
Steff

I have the same problem, My docker0 bridge is on the right range and --bip works fine for that. All works fine, I can start and stop containers happily and still talk to my machines on the 172.17 range. But, if I use docker-compose to bring up a group of containers, it will create a new bridge and this will be on the 172.17 range.