-
Notifications
You must be signed in to change notification settings - Fork 119
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Docker image dotnet-isolated #441
Comments
Updated the description. |
I'm having the same problem, running a v3 Functions App using Docker (same image as you) with dotnet-isolated runtime. I've got a ticket open with MS to try solve this. I have tried deploying completely new AppService/ResourceGroup/FunctionsApp but still no luck, Did you get anywhere with your issue? |
@dfibuch, |
@lKoTl Fair enough. I just got off the phone with MS Azure support to show them exactly what is going on and it'll be getting escalated. Will update here if/when I hear back from them. |
Possibly related: Azure/azure-functions-dotnet-worker#524 |
Thank you for linking this, it has actually fixed my issue, |
I'm using Functions as dotnet-isolated locally and it works fine.
I wish to host it with a docker container, so went straight to the dotnet-isolated images.
I have 2 Timer Trigger functions and 1 Queue Trigger function.
When using
FROM mcr.microsoft.com/azure-functions/dotnet-isolated:3.0
image I get missing compatible framework version and gRPC fails.Comparing the
dotnet
anddotnet-isolated
:I hope to get some assistance with this.
UPDATE
I went installing
aspnetcore-runtime-5.0
into the image manually, so the functions now are starting.New issue that I'm hitting:
UPDATE 2
Solved the gRPC startup issue with the 15733 image.
Next problem:
The text was updated successfully, but these errors were encountered: