You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Recently I have been trying out Docker Swarm in a mixed node environment, since I have some Windows containers that I need to run. I have multiple Linux containers behind a service, so that the traffic will be load balanced. As long as i access this containers from Linux nodes or the Ingress it is load balanced as expected. But when I call the service from Windows containers, it always takes the first container listed in the service.
Reproduce
Create a swarm with one Linux and one Windows node
Deploy the example compose file as a stack (example file below)
From the Linux Container run curl nginx multiple times. You can see that the load balancing works, since the response is the containers hostname. So it switches between the two nginx containers.
From the Windows container run irm nginx multiple times. You can see that the response is always the same. Even though it should balance the load.
Description
Hello,
Recently I have been trying out Docker Swarm in a mixed node environment, since I have some Windows containers that I need to run. I have multiple Linux containers behind a service, so that the traffic will be load balanced. As long as i access this containers from Linux nodes or the Ingress it is load balanced as expected. But when I call the service from Windows containers, it always takes the first container listed in the service.
Reproduce
curl nginx
multiple times. You can see that the load balancing works, since the response is the containers hostname. So it switches between the two nginx containers.irm nginx
multiple times. You can see that the response is always the same. Even though it should balance the load.compose file:
nginx.conf:
Expected behavior
Load balancing should also work from Windows containers
docker version
Windows node:
Linux node:
docker info
Windows node:
Linux node:
Additional Info
No response
The text was updated successfully, but these errors were encountered: