-
Notifications
You must be signed in to change notification settings - Fork 289
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
Hybrid swarm routing mesh not working #3052
Comments
@stevenmiller first of I can see that this is your first issue on GitHub so let me say welcome :) Then some side comments (which you don't need to comment but maybe it is good idea to check them out):
Then what comes to this issue, IMO your stack file looks to be just like documentation says that how it should work but in real life it looks that Windows implementation of overlay network / components used behind it (example: hcsshim) have some undocumented weaknesses. |
@olljanat Thanks for the tips! We are revising the apps to run what we can on linux containers. At least one service requires Windows so we are stuck with it for the time being. Is there any further troubleshooting you can advise with this current setup or is likely just an issue we will have to wait out? |
Just as a note: with my org's Microsoft SA agreement we get support, so I have a technical support case open regarding this issue. I will update with the resolution (if one is found). |
Depending on your application architecture (which apps need to be able to talk which apps) you can example place Windows and Linux containers to same overlay network so they can talk with each others inside of it.
OK. It is really interesting to hear if they are solve this issue as my earlier experiences of level of Microsoft support have not been too positive. |
Here's the final email from MS support. Unfortunately no resolution at this time, however we did find that if you deploy a container and expose the default port (say 80 for IIS) it is reachable from both nodes without a problem. It seems to be an issue with the port translation between hosts. :
|
Btw is this related to moby/moby#38484 ? |
Issues go stale after 90d of inactivity. Prevent issues from auto-closing with an If this issue is safe to close now please do so. Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows. |
Closed issues are locked after 30 days of inactivity. If you have found a problem that seems similar to this, please open a new issue. Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows. |
Howdy!
I have a two node hybrid swarm, with one Ubuntu Linux 18.04 node acting as manager and one Windows 2019 node participating as a worker. We have a sample environment we are testing which are entirely Windows containers. We are able to reach the published port for these services from the Windows node (ex. 10.20.1.121:8888) but we are unable to from the Linux node (ex. 10.20.1.122:8888). Our understanding of the ingress mesh networking is that this should work fairly seamlessly as it will route traffic within the swarm to the correct node.
This issue is also occurring with the swarmpit UI stack we have deployed to the swarm. The UI (10.20.1.122:888) is not able to be reached from the Windows node IP (10.20.1.121:888).
Expected behavior
Services running on one node should be accessible from published port on another node
Actual behavior
Published Windows container services are not accessible from linux node and vice versa
Information
Published services and ports:
Both the environment we have pulled from a private repo and the swarmpit stack exhibit this behavior. I am unable to reach the swarmpit UI from port 888 on the Windows node IP.
Steps to reproduce the behavior
Here is the stack with our private repo removed:
teststack.zip
Let me know if I can provide any other info.
The text was updated successfully, but these errors were encountered: