Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Too many networks #637

Open
cybersolutionsllc opened this issue Mar 31, 2023 · 1 comment
Open

Too many networks #637

cybersolutionsllc opened this issue Mar 31, 2023 · 1 comment
Labels
bug Something isn't working

Comments

@cybersolutionsllc
Copy link

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

  1. cd to site directory
  2. run "warden env up"
  3. 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.

@cybersolutionsllc cybersolutionsllc added the bug Something isn't working label Mar 31, 2023
@navarr navarr added this to Warden Mar 31, 2023
@navarr navarr moved this to 🆕 New in Warden Mar 31, 2023
@navarr navarr changed the title warden env up Too many networks Mar 31, 2023
@navarr
Copy link
Member

navarr commented Mar 31, 2023

Maintainer Note: Puffin solved this issue by supplying a specific subnet puffinrocks/puffin@77be2d4

A workaround is available by configuring the default rangers https://serverfault.com/questions/916941/configuring-docker-to-not-use-the-172-17-0-0-range

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Status: 🆕 New
Development

No branches or pull requests

2 participants