azure-functions-dotnet-worker: Functions do not work when using the `dotnet-isolated:4-dotnet-isolated6.0` base image.

I’m trying to deploy an Azure Functions app (net6.0 isolated functions v4) to Azure (Linux P1v2 app service plan). the app is containerized with mcr.microsoft.com/azure-functions/dotnet-isolated:4-dotnet-isolated6.0 base image. i’m deploying and see logs in deployment center showing that the image was downloaded and container started. but no functions have been found and i get this error notification in the azure portal:

Microsoft.Azure.WebJobs.Script: WorkerConfig for runtime: dotnet-isolated not found.

i can’t find any docs whatsover around setting up deployments to azure for functions v4 aside from deploying straight from vs code using the extension (not what i want to do). im trying to setup deployment of a production application from CI/CD using terraform

thanks

About this issue

Original URL
State: closed
Created 2 years ago
Reactions: 8
Comments: 24 (7 by maintainers)

Most upvoted comments

@ihordyrman Could you try deploying using function core tools and see that makes a difference?

Deploying with func azure functionapp publish seems to work. However deploying the resource with Bicep/ARM and then using the AzureFunctionApp@1 Azure pipelines task to deploy the function app results in the error.

drmathias on Mar 10, 2022

I’ve got the same issue. However, it actually used to work for us. But after a redeploy, we started getting this issue.

Our function isn’t containerized though. So it is not only for containerized function. However, we are using .NET 6.0, dotnet-isolated and extension version 4, so it sounds a LOT like the same issue.

I’ve tried re-deploying the whole app service, but it just comes back with the same issue. Any information would be appreciated!

ChrisKlug on Feb 21, 2022

Deployment with the fix (for non-app service images) has been completed. The Microsoft.AspNetCore.App framework should be present in the mcr.microsoft.com/azure-functions/dotnet-isolated:4 image now.

Let us know if you run into issues.

kshyju on May 9, 2022

Just wanted to provide an update here. The full deployment with updated images addressing this issue should complete this week.

We’ll close this issue with an update when that is done.

fabiocav on Mar 23, 2022

I was able to resolve the issues on my end via this comment in issue #556.

Basically, I’m using Azure App Configuration with keyvault linked values, and the keyvault access policy did not exist.

This exception is extremely generic and seems to be thrown for ANY startup issue. There is definitely a need for the logging/exception handling during isolated functions startup to be drastically imrproved.

jkdmyrs on Mar 8, 2022

We are facing this issue as well, but in our case, we don’t use a docker image. We are creating and configuring Azure resources via the ARM template. A similar issues are here #821, #819

@fabiocav any updates on this? The comment you’ve linked is more than two weeks old and the issue is still here.

ihordyrman on Mar 7, 2022