File handle of executable is not closed after execution of the file if the file is on a docker volume

[friedrichatgc]

Describe the bug
When a container executes a executable file (*.exe) which is placed inside a docker volume than vmwp.exe keeps a open handle to this file forever (until the container exists).
Hence, e.g. deleting the file after the executable has finished is not possible.
(at least if the container is running in HyperV isolation)

To Reproduce
Run the following steps in a cmd shell:

REM create a host-dir for a docker volume
mkdir .\content

REM copy a executable to the host-dir of a docker volume
copy c:\Windows\System32\xcopy.exe .\content

REM run a docker container which executes the above executable and then tries to delete this executable -> ERROR the executable is still opened by vmwp.exe
docker.exe run --isolation=hyperv -v .\content:c:/content mcr.microsoft.com/windows/nanoserver:ltsc2019 cmd /c "c:\content\xcopy.exe & del c:\content\xcopy.exe"

Expected behavior
The del command should not fail with the error message "Access is denied".
The reason for this seems to be that vmwp.exe still has a open handle to xcopy.exe.
It works if the executable is not on a docker volume but stored direct in the container.
It also works if the executable is not executed before the delete.

Configuration:

• Edition: Windows 10 Pro
• Base Image being used: nanoserver:ltsc2019
• Container engine: docker
• Container Engine version docker 27.3.1 (server and client)

[github-actions]

Thank you for creating an Issue. Please note that GitHub is not an official channel for Microsoft support requests. To create an official support request, please open a ticket here. Microsoft and the GitHub Community strive to provide a best effort in answering questions and supporting Issues on GitHub.

[ntrappe-msft]

@friedrichatgc Hey, thanks for bringing this up. We'll repro this as soon as we can.