Azure Functions Docker 部署 Linux 工作人员在资源组中不可用
Azure Functions Docker Deployment Linux workers are not available in resource group
正在尝试通过函数应用从 Azure 容器注册表部署 nginix 容器，
出现错误，
Linux workers are not available in resource group
如何启用 linux 工作人员到资源组？
用于部署的 Dockerfile，
FROM nginx
COPY dist /usr/share/nginx/html
您似乎不能在同一个资源组中同时拥有 linux 和 windows 资源
There is a current limitation in regards to not mixing Windows and
Linux apps in the same resource group as well.
https://docs.microsoft.com/en-us/azure/app-service/containers/app-service-linux-intro#limitations
所以你目前唯一的选择是为 linux 资源
创建一个新的资源组
[更新2022-02-16]
现在似乎可以在 Linux 和 Windows 应用服务计划之间共享资源组：https://docs.microsoft.com/en-us/azure/app-service/overview#limitations
[原创]
无法在同一资源组和同一位置创建 linux 应用服务计划和 windows 应用服务计划，但您可以使用相同的资源组并将两个计划部署在不同的位置。
Based on a current limitation, for the same resource group you cannot mix Windows and Linux apps in the same region.
https://docs.microsoft.com/en-us/azure/app-service/containers/app-service-linux-intro#limitations
尽管我发现如果您在创建 linux 应用程序服务计划。在同一位置创建证书之前，您必须创建 linux 应用服务计划。
如果您在不同区域为 LINUX 应用创建应用服务计划（尽管资源组可以与 Windows 应用服务计划位于同一区域），它应该仍然有效。
In some cases, when trying to create a Function App, you may receive the following error...
- you're creating the Function App in an existing resource group
- this resource group already contains regular (i.e. non-Dynamic or Premium) Web Apps in the same region that you're trying to create the Function App. This can even occur if you are creating a Azure Functions Premium Plan in a resource group that has an App Service Premium Plan of the same OS.
- the scale unit that those non-Dynamic or Premium resources are in does not yet support this SKU
- you are attempting to create a Linux Consumption app in a resource group with any other app service plan type.
...
Even in some situations we have pools specifically for one plan. For example, Linux consumption stamps can only run linux consumption apps, so you aren't able to place a linux consumption plan in the same resource group as any other app service plan. The functions themselves can be in the same resource group, but the plan cannot be.
参考
正在尝试通过函数应用从 Azure 容器注册表部署 nginix 容器，
出现错误，
Linux workers are not available in resource group
如何启用 linux 工作人员到资源组？
用于部署的 Dockerfile，
FROM nginx
COPY dist /usr/share/nginx/html
您似乎不能在同一个资源组中同时拥有 linux 和 windows 资源
There is a current limitation in regards to not mixing Windows and Linux apps in the same resource group as well.
https://docs.microsoft.com/en-us/azure/app-service/containers/app-service-linux-intro#limitations
所以你目前唯一的选择是为 linux 资源
创建一个新的资源组[更新2022-02-16]
现在似乎可以在 Linux 和 Windows 应用服务计划之间共享资源组：https://docs.microsoft.com/en-us/azure/app-service/overview#limitations
[原创]
无法在同一资源组和同一位置创建 linux 应用服务计划和 windows 应用服务计划，但您可以使用相同的资源组并将两个计划部署在不同的位置。
Based on a current limitation, for the same resource group you cannot mix Windows and Linux apps in the same region.
https://docs.microsoft.com/en-us/azure/app-service/containers/app-service-linux-intro#limitations
尽管我发现如果您在创建 linux 应用程序服务计划。在同一位置创建证书之前，您必须创建 linux 应用服务计划。
如果您在不同区域为 LINUX 应用创建应用服务计划（尽管资源组可以与 Windows 应用服务计划位于同一区域），它应该仍然有效。
In some cases, when trying to create a Function App, you may receive the following error...
- you're creating the Function App in an existing resource group
- this resource group already contains regular (i.e. non-Dynamic or Premium) Web Apps in the same region that you're trying to create the Function App. This can even occur if you are creating a Azure Functions Premium Plan in a resource group that has an App Service Premium Plan of the same OS.
- the scale unit that those non-Dynamic or Premium resources are in does not yet support this SKU
- you are attempting to create a Linux Consumption app in a resource group with any other app service plan type.
...
Even in some situations we have pools specifically for one plan. For example, Linux consumption stamps can only run linux consumption apps, so you aren't able to place a linux consumption plan in the same resource group as any other app service plan. The functions themselves can be in the same resource group, but the plan cannot be.