You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
"ERROR: could not find an available, non-overlapping IPv4 address pool among the defaults to assign to the network"
To Reproduce
cd to site directory
run "warden env up"
Error is produced during Traefik start
Expected Behavior
Expected behavior would be no error and the warden env up command works
Additional context
I'm running a large number of different builds for this site. Based on my initial review this issue has to do with warden creating a new network for every time that a build is created. According to docker documentation there is only 31 available networks that can be used.
It would be preferable to be able to specify a network name to use for builds somehow. That way all my builds can use the same network without burning up the 31 available networks.
The text was updated successfully, but these errors were encountered:
Version of Warden
0.12.0
Operating System and Installation Method
Ubuntu 22.04.1
Describe the Bug
"ERROR: could not find an available, non-overlapping IPv4 address pool among the defaults to assign to the network"
To Reproduce
Expected Behavior
Expected behavior would be no error and the warden env up command works
Additional context
I'm running a large number of different builds for this site. Based on my initial review this issue has to do with warden creating a new network for every time that a build is created. According to docker documentation there is only 31 available networks that can be used.
It would be preferable to be able to specify a network name to use for builds somehow. That way all my builds can use the same network without burning up the 31 available networks.
The text was updated successfully, but these errors were encountered: