Open gabrieltalavera opened 5 years ago
I think you template is invalid. In this case is telling you that you are setting the location twice, one in the resource and one in the service, which is incorrect, you should set it only at resource level.
Follow this:
And btw, there is a new API version for Mesh templates.
Cheers
I do have the exact same issue, unfortunately there is no location
property present anywhere within the service model.
"properties": {
"description": "Service Fabric Mesh Translate Application!",
"services": [
{
"type": "Microsoft.ServiceFabricMesh/services",
"name": "TranslateService",
"properties": {
"description": "Service Fabric Mesh TranslateService Application!",
"osType": "linux",
"codePackages": [
{
"name": "TranslateServiceCode",
"image": "TranslateServiceImage",
"endpoints": [
{
"name": "TranslateServiceListener",
"port": "443"
}
],
"resources": {
"requests": {
"cpu": "1",
"memoryInGB": "1"
}
}
}
],
"replicaCount": "1",
"networkRefs": [
{
"name": "[resourceId('Microsoft.ServiceFabricMesh/networks', 'TranslateNetwork')]"
}
]
}
}
]
}
Any thoughts?
I'm having the following error when trying to deploy a Service Fabric Mesh template:
This template seems to be the only one that doesn't work, although I cannot find out why is it. Is there any restriction when using Linux based docker containers in Service Fabric Mesh?