search

docker-flow / docker-flow-proxy

Docker Flow Proxy
https://docker-flow.github.io/docker-flow-proxy/
MIT License
317 stars 189 forks source link

IP address exhaustion #88

Closed jwalkins2017 closed 2 years ago

jwalkins2017 commented 5 years ago

Description

I am replicating multiple test environments behind a single DFP instance and have hit an IP exhaustion issue with all the containers being on the same "proxy" network. Is it possible to partition out the networks or have multiple DFP for each environment on the same swarm?

Steps to reproduce the issue:

  1. Have more that 200 containers behind the DFP

Describe the results you received: Containers are stuck in the new task.

Describe the results you expected: Containers should start up normally.

Additional information you deem important (e.g. issue happens only occasionally): Once I removed an environment, I was able to start up other containers.

vfarcic commented 5 years ago

That sounds like a problem with Swarm's Overlay network that is somewhat limited in certain providers. Where are you running your cluster?

jwalkins2017 commented 5 years ago

I am running it in an on-prem cluster, 5 nodes, docker 18.06.1~ce

jwalkins2017 commented 5 years ago

To add a more context, DFP has a single network assigned to it "Proxy", any container that is behind DFP is also on the "Proxy" network. Is it possible to assign multiple networks to the DFP container and then assign the load balanced containers on those networks? For example: DFP: network proxy - external internal

Nginx: network internal

vfarcic commented 5 years ago

This project needs adoption. I moved to Kubernetes and cannot dedicate time to this project anymore. Similarly, involvement from other contributors dropped as well. Please consider contributing yourself if you think this project is useful.

lle0x commented 2 years ago

Dear @jwalkins2017

If this issue is still relevant, please feel free to leave a comment here.

lle0x commented 2 years ago

Closed due to inactivity