Hey guys, I was happily running 44 docker containers for a while on Debian host. Today I tried to add a new service (uptime-kuma) using portainer stacks, but I got this error:

Error response from daemon: could not find an available, non-overlapping IPv4 address pool among the defaults to assign to the network

Quick google led me to this link where I found possible problem with max number of docker networks. I did docker network prune, it removed 5 networks that were not in use and viola, uptime-kuma is working now!

Am I reaching the limit? What to do if I need 10 more services on the same host? I bet I saw some people in this community running many more services

  • @[email protected]
    link
    fedilink
    English
    49 months ago

    I’m pretty sure all of those entries are in the same /12 network - 172.16.0.0/12. Apparently there’s nothing wrong with it, but I think you can significantly simplify that config by just removing all the extra ones

    • @[email protected]
      link
      fedilink
      English
      6
      edit-2
      9 months ago

      Could simplify it by making a 28 block at most. That is 14 IPs per bridge which seems like way more than one would generally need anyhow.

      {
        "default-address-pools": [
          { "base":"172.16.0.0/12", "size":28 },
        ]
      }
      
      • @5PACEBAR
        link
        English
        39 months ago

        Had to do exactly that last week when I hit Docker’s rather low network limit.