`func init --docker` generates old version of Dockerfile for C# isolated

Customers are reporting (and I’ve also verified) that func init --worker-runtime dotnet-isolated --docker is generating what seems to be an older Dockerfile:

FROM mcr.microsoft.com/dotnet/sdk:5.0 AS installer-env

# Build requires 3.1 SDK
COPY --from=mcr.microsoft.com/dotnet/core/sdk:3.1 /usr/share/dotnet /usr/share/dotnet

COPY . /src/dotnet-function-app
RUN cd /src/dotnet-function-app && \
    mkdir -p /home/site/wwwroot && \
    dotnet publish *.csproj --output /home/site/wwwroot

# To enable ssh & remote debugging on app service change the base image to the one below
# FROM mcr.microsoft.com/azure-functions/dotnet-isolated:3.0-dotnet-isolated5.0-appservice
FROM mcr.microsoft.com/azure-functions/dotnet-isolated:3.0-dotnet-isolated5.0
ENV AzureWebJobsScriptRoot=/home/site/wwwroot \
    AzureFunctionsJobHost__Logging__Console__IsEnabled=true

COPY --from=installer-env ["/home/site/wwwroot", "/home/site/wwwroot"]

The in-process version uses the correct base image, but both still reference mcr.microsoft.com/dotnet/core/sdk:3.1 which I’m pretty sure is no longer supported.

This bug is affecting all customers using func.exe to generate Dockerfiles for their C# isolated worker process function apps.

[khkh-ms]

Please install the latest version which should be 4.0.5198.

[ggailey777]

Verified that 4.0.5.5198 fixes the issue. Thanks @khkh-ms I’ll update the container docs to note the func.exe version requirement.