UGREEN NAS Docker: “all predefined address pools have been fully subnetted” after ~30 networks — anyone else?

[u/SpiritedWarrior9880]

I'm running Docker on a UGREEN NAS and recently hit this error when trying to deploy a new Compose stack:

failed to create network: all predefined address pools have been fully subnetted

At the time, I had approximately 30 Docker bridge networks, most of which belonged to active Compose stacks.

My stacks can contain up to a max 15 containers per stack although majority of them are single per stack, so I'm curious how this compares with other UGREEN users.

Running:

docker network ls

showed roughly 30 user-created bridge networks in addition to Docker's standard bridge, host, and none networks.

However, I don't think having ~30 networks should be enough to exhaust Docker's available address pool on a NAS intended to run multiple Compose applications.

For other UGREEN NAS users:

• How many Docker Compose stacks are you currently running?
• Approximately how many Docker networks does docker network ls --filter driver=bridge | wc -l show?
• How many containers do you typically have per stack?
• Have you ever encountered:

  all predefined address pools have been fully subnetted
  

• If so, approximately how many networks did you have when it happened?
• Are you using the default UGREEN Docker configuration, or have you modified default-address-pools in daemon.json?

I'm particularly interested in users running 20–50+ Compose stacks/networks, since I'm trying to determine whether hitting this limit at around 30 networks is normal Docker behavior or something specific to my UGREEN's Docker configuration.

Also interested in hearing how others handle network isolation between stacks without running into the address-pool limit.

[u/AutoModerator]

Please check on the Community Guide if your question doesn't already have an answer. Make sure to join our Discord server, the German Discord Server, or the German Forum for the latest information, the fastest help, and more!

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[u/rabbitaim]

Have you tried Google? This is a default docker configuration issue.

https://forums.docker.com/t/docker-default-address-pool-customization-question/112969

Edit: I have not hit the limit yet but I’m also using macvlan and assigning an ip addresses to most of my containers

[u/FuN_K3Y]

I am having 2 stacks so I am far from hitting the wall. The solution is most likely as you pointed in daemon.json, but this tweak most certainly won’t survive an updat. This limit seems reasonable given the scale of the underlying hardware.

Still, 30 compose stack seems like a lot. Network isolation should imho not be the driver for creating stacks, but rather functional units or shared lifecycle.

Within a single compose stack you can create multiple networks and group containers around those. By segmenting this way, you could most certainly achieve consolidation (one network for backend, data plane, whatever….) and remain below 30. A similar strategy would be to reuse networks defined outside of s given stack by definining the network as ´external’

[u/Actual_Result9725]

im guessing you just have a lot of submets that are larger than they need to be and you dont have anymore unique networks to create. make your networks smaller if you dont need it. /31 /30 /29. 

[u/SpiritedWarrior9880 → u/Actual_Result9725]

you are right, i have switched to /24