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
IPv4 pool is full #184
Comments
Do you happen to have a line If you do have it, try commenting that line out. Looks like it may impact IPv4 somehow: moby/moby#30295 (comment) |
Well, server has IPv6 DNS servers and I removed them but no effect. |
By default there can be only about 30 docker networks created on a host: moby/moby#23971 (comment) https://github.com/docksal/service-vhost-proxy provides several very useful features when used in a CI environment. See the README in that repo.
This resolves the network limit issue as long as you have less than 30 environments on a single host being active at the same time. Here's how our Docksal sandbox servers are configured:
|
I had this same issue, and resolved it by ssh-ing into the boot2docker instance. Then running |
@claytron5000 you can run |
I'm using docksal for local developent and for CI and right now we have 29 docksal project running on one host. When I run fin up I get this error:
If I remove few projects and run fin cleanup IP pool get some space and this project starts.
Question is how I can increase IP pool for docksal?
Right now we do not need more than 15 IP adresses per project.
Output of
fin config
:fin config output
Output of
fin sysinfo
:fin sysinfo output
The text was updated successfully, but these errors were encountered: