Guest service in container cannot connect to service fabric cluster. RRS feed

  • Question

  • I am using this sample https://github.com/Azure-Samples/service-fabric-dotnet-containers in a local dev deployment.

    FrontEndService in the container wasn’t able to connect service fabric cluster on the HOST.

    Can someone please help what’s going on here.

    Below is the log

    ServiceName Container.Application/BackEndService, GatewayPort 19080



    Listen address is

    HttpListener started

    Node Name is _Node_2

    Received a request.

    About to call Gateway:$/ResolvePartition?api-version=1.0

    Exception occurred Unable to connect to the remote server

    Wednesday, March 22, 2017 6:51 AM


  • Looking at the IP, are you running it on your local box? Today, Windows Containers cannot talk to the host machine, so that could be the issue you are hitting.  While the Windows team fixes the bug, please try deploying to a cluster in Azure. 


    Wednesday, March 22, 2017 5:29 PM
  • Can you first try deploying the sample to Azure and verify it works? That will help us troubleshoot. 

    While the sample does work around the issue I mentioned earlier (host not able to talk to the guest container),  one issue could be  that the onebox cluster uses localhost for NodeIPAddressOrFQDN in the cluster manifest. 

    You can do either of the 2 things:

    1.       Deploy on azure where we setup the node ip address correctly.

    2.       If deploying onebox deploy using IPAddress for Node instead of localhost in the cluster manifest.

    If #1 works, then we can pretty much confirm that's the issue. For #2, you can deploy/create you r cluster using the HOST IPAddress instead of localhost using instructions @ https://docs.microsoft.com/en-us/azure/service-fabric/service-fabric-cluster-creation-for-windows-server.

    We'll update the sample doc to make this clearer.


    Thursday, March 23, 2017 4:45 AM

All replies