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

Lando starts removing old networks because of Docker's network limit #244

Open
Vandaahl opened this issue Jul 20, 2021 · 5 comments · May be fixed by #245
Open

Lando starts removing old networks because of Docker's network limit #244

Vandaahl opened this issue Jul 20, 2021 · 5 comments · May be fixed by #245
Labels
bug Something isn't working Needs Triage

Comments

@Vandaahl
Copy link

I am running Lando v3.1.4 on Debian 10 and have a few dozen Lando apps. I run a nightly script that backups all the databases of my Lando apps, so all apps are started and then stopped when the script has finished. In the morning, when I manually start some apps I'm working on, chances are that one of them will complain that "Lando has detected you are at Docker's network limit!" and it starts removing some old networks. Consequently, I will have to rebuild other apps that have their network removed on a daily basis.

I thought I could get around this by increasing the Docker network limit, so I followed theses suggustions and created /etc/docker/daemon.json with the following contents:

{ "bip": "10.200.0.1/24", "default-address-pools":[ {"base":"10.201.0.0/16","size":24}, {"base":"10.202.0.0/16","size":24} ] }

This should increase the Docker network limit by the hundreds, if I understand correctly, yet Lando does not seem to be aware of this because it is still complaining about the Docker network limit. Is there anything else I can try to increase my network limit? Or is this a limitation of Lando?

@Vandaahl Vandaahl added the bug Something isn't working label Jul 20, 2021
@stale
Copy link

stale bot commented Mar 30, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions and please check out this if you are wondering why we auto close issues.

@stale
Copy link

stale bot commented May 23, 2023

We haven't heard anything here for about a year so we are automatically closing this issue to keep things tidy. If this is in error then please post in this thread and request the issue be reopened!

@stale stale bot closed this as completed May 23, 2023
@jerome-pilotin
Copy link

We are using lots of Lando sites for development purposes with a small team, and we are hitting this issue consistently.
I have followed the same suggestions, but the situation hasn't changed. The bridge network doesn't seem to be respecting this.

Does anyone have an idea to fix this issue?

@Mgrmjp
Copy link

Mgrmjp commented Oct 22, 2024

Anything regarding this?

@rtfm-47 rtfm-47 transferred this issue from lando/lando Oct 22, 2024
@reynoldsalec
Copy link
Member

@Mgrmjp it looks like Lando hardcodes the network limit to 32. Makes sense this would be an issue if you're running A LOT of sites and want to modify the Docker Daemon to satisfy.

I spun up a PR that I think should address the issue by allowing users to set a networkLimit global config parameter: #245

I'm going to chat to @pirog and get his feedback on the PR, hopefully can move this forward in the next stable release.

@reynoldsalec reynoldsalec reopened this Oct 22, 2024
@pirog pirog linked a pull request Oct 25, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working Needs Triage
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants