4.3.0 based docker image stopped working with error Cannot access a disposed object. Object name: 'IServiceProvider'.

[softnado]

Version

Azure Functions Core Tools
Core Tools Version: 4.3.0+df07acf9d837d635d1efc2c973225f4f1c8a4333 (64-bit)
Function Runtime Version: 4.1042.100.25374

Description

We built one docker image packed the core tools 4.3.0 about 13 days ago and everything working but today when we restart the container, it start failing with error:

Skipping 'AzureWebJobsScriptRoot' from local settings as it's already defined in current environment variables.
Cannot access a disposed object.
Object name: 'IServiceProvider'.

The problem is that there is no other changes at all and image worked two weeks ago but today this error happened for both dotnet version and python version when restart container.

Because there is no other print at all, would like to check what can be looked for root cause?

Steps to reproduce

Custom build docker image using dockerfile like this:

---

FROM mcr.microsoft.com/windows-cssc/python:3.13-servercore-ltsc2022 AS base

SHELL ["cmd", "/S", "/C"]

Install .Net 8 Runtime

RUN curl.exe -L https://builds.dotnet.microsoft.com/dotnet/Sdk/8.0.413/dotnet-sdk-8.0.413-win-x64.exe --output dotnet-sdk-8.0.413-win-x64.exe
RUN C:\dotnet-sdk-8.0.413-win-x64.exe /install /quiet /norestart
RUN del C:\dotnet-sdk-8.0.413-win-x64.exe

Install Azure Function Core Tools

RUN curl.exe -L https://go.microsoft.com/fwlink/?linkid=2174087 -o func-cli-x64.msi
RUN msiexec /i C:\func-cli-x64.msi /quiet /qn /norestart
RUN del C:\func-cli-x64.msi

Install VC Runtime for Numpy DLL Dependencies

RUN curl.exe -L https://aka.ms/vs/17/release/vc_redist.x64.exe --output vc_redist.x64.exe
RUN vc_redist.x64.exe /install /quiet /norestart
RUN del C:\vc_redist.x64.exe

COPY . /AzFunc
RUN python -m pip install --upgrade pip
RUN python -m pip install --upgrade setuptools
RUN python -m pip install -r /AzFunc/requirements.txt

ENV AzureWebJobsScriptRoot=/AzFunc
ENV AzureFunctionsJobHost__Logging__Console__IsEnabled=true
ENV FUNCTIONS_WORKER_RUNTIME=python
ENV PYTHONDONTWRITEBYTECODE=1
ENV PYTHONUNBUFFERED=1

WORKDIR /AzFunc
ENTRYPOINT [ "func", "host", "start"]

---

Environment variables been injected when launch the container and no changes there.

Some debug version output>

And it seems indicate have something to do with Code section below, looking for suggestions?

[softnado]

Confirmed the issue is caused by the WDAC Enforce Mode (Code Integrity). Though the actual root cause is under investigation. Looking for suggestions.