-
Notifications
You must be signed in to change notification settings - Fork 18
Ability to obtain client IP address on container HTTP requests #7
Comments
@rocketraman The behavior you are observing is due to moby/moby#25526 You can try the temporary workaround of specifying |
Closing since this a duplicate of moby/moby#25526 |
@ddebroy I tried this workaround. It seems that publishing the port with In addition, the externalLoadBalancer backend pool only goes to the worker nodes, but if something like |
Thanks for the hints, I have managed to get this working (leaving my setup below to help someone else) Im using Traefik for proxy/acme
Then you need to configure the service to by-pass the ingress mesh, using host mode ports
Then I manually added port 80+443 to the azure load balancer that points at the manager nodes |
When deploying containers into Docker for Azure, it appears like there is no way to obtain the original client IP address for HTTP requests. The container sees only the internal Docker network address e.g.
10.0.x.x
.Normally, this would be handled via
X-Forwarded-For
headers, but by the time the request reaches an haproxy container, the source IP is already obscured.Is there a solution?
The text was updated successfully, but these errors were encountered: