-
-
Notifications
You must be signed in to change notification settings - Fork 127
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
error="could not find an available IP while allocating VIP" #35
Comments
As I understand dnsrr solve this problem but it does not support with traefik right now traefik/traefik#3288 |
Thanks for reporting back and closing the issue 👍 |
dnsrr works for me with the latest version of Traefik and Docker |
I will just save everyone a TON of time. Ingress default creation is the problem here. Every service you start up connects to your created network and the This can be tested by launching a swarm with Keep in mind if one wants to reduce the number of ip address assigned by default on network create then you can set the mask length parameter of the swarm, then remove the ingress network, and recreate it with subnet Thumbs up if this helped! |
In my environment, we solved this by creating more networks and linking to traefik, so we could use another 256 available addresses for each network created; traefik-docker-compose.yml
my api.yml 1:
my front.yml after 256 services:
|
error="could not find an available IP while allocating VIP"
I get this error every day on my dev single server environment because all my "public" services(about 100 services) use traefik-public.
docker/ip-util-check script say that:
Network traefik-public/n37oijkbobyw has an IP address capacity of 253 and uses 220 addresses spanning over 1 nodes
WARNING: network is using more than the 75% of the total space. Remaining only 32 IPs after upgrade
What can I do in this situation?
The text was updated successfully, but these errors were encountered: