Compatibility issues with Windows Server 2019, Azure Service Fabric / Mesh 6.4 and Docker 18.09.3

[MedAnd]

Installing Azure Service Fabric / Mesh on the same local VM running Docker and Portainer causes Docker to be unstable. For example when I create or remove a local Mesh cluster, the Portainer container stops running. Also worth noting is that I have configured Docker to run both Windows and Linux containers (LCOW).

Creating or Removing a Mesh or Service Fabric cluster seems to interfere with docker, for example containers already running show the following error:

Once the Service Fabric / Mesh cluster is created, the containers come back up.

Other Details:

Service Fabric / Mesh Version | 6.4.617.9590
OS Information | windows x86_64 Windows Server 2019 Standard Version 1809 (OS Build 17763.379)
Kernel Version | 10.0 17763 (17763.1.amd64fre.rs5_release.180914-1434)
Docker Version | 18.09.3
Portainer Version | 1.20.2

cc @masnider @mikkelhegn @raunakpandya

[mattrowmsft]

I think SF assumes complete ownership of the container runtime on your OS when it is running. I'm not sure how well side by side scenarios will work b\c of that.

[MedAnd]

@mattrowmsft - appreciate the insight. Wondering if this is documented anywhere? I expected mesh to own only the containers it knows about, were deployed via mesh... does this mean any local cluster with Service Fabric / Mesh installed cannot use other docker tooling & workflows, everything must go via SF Mesh?