title: What happens when docker daemon runs out of network IP addresses to allocate when deploying compose environments?
body: <p>Currently, we are deploying a compose environment stack to an ubuntu server. In the compose file, we are not defining an address and utilizing the underlying default docker bridge network that docker compose comes with out of the box.</p>
  
  <p>When we deploy our compose environment to a development server (IP range 10.x.x.x), the base <code>docker0</code> network address starts at <code>172.17.0.0</code>.</p>
  
  <p>For every subsequent deployment, the address is incremented, (i.e. <code>172.18.0.0</code>, and then <code>172.19.0.0</code>) - this is expected.</p>
  
  <p>My question is, what happens when the daemon runs out of addresses to allocate, does the process just start back over at <code>172.17.0.0</code>? Or does something else occur? I have been unable to find any of this information in the documentation. </p>
  
  <p>Basically, I want to know if this is something I should be proactive about, rather than reactive when a problem occurs. </p>
  
  <p>Thank you in advance!</p>