Visual studio build fails while copying files to the bin directory due to file locks by vmwp.exe

user_6421230 0
Viewed 920

I'm running my development environment in Docker containers. Since I have done some updates I'm now experiencing some difficulties when trying to rebuild my project that's running in my Docker container.

My project is running in a Windows Server Core Docker container running IIS, and I'm running the project from a shared volume on my host. I'm able to build the project before starting the docker container, but after the docker container is started the build fails with the following error:

Could not copy "C:\path\to\dll\name.dll" to "bin\name.dll". Exceeded retry count of 10. Failed. The file is locked by: "vmwp.exe (22604), vmmem (10488)"

It seems that the Hyper-V process is locking the DLL files. This clearly wasn't the case before and this seems to be related to some Docker or Windows updates I have done. How can I solve this issue? Do I need to change the process of building the application and running it in my Docker containers?

I have been searching for a while now, and I can't find much about this specific issue. Any help would be appreciated. Thanks in advance!

hyper-v windows-10 docker locking
2 Answers

I've run in the similar problem. Solved by stopping/removing the running application container from docker-for-windows interface. docker rm -f will also do.

user_20488240

Potential solution:

  1. If you use Docker Windows Containers make sure you have at least Windows 10.0.1809 on both environment(your physical machine and on docker) -run CMDs and you will see on top of it.
  2. Use isolation flag with process when you run docker: --isolation process.

On physical machine two vmxxx(lower and higher PID)(don't remember the name exactly) processes was keeping *.dll file(the build was going on docker side where build tools 2019 was used).

Short description:

  1. First MSbuild Error occurred because msbuild tries to delete file - access denied - probably this one vm process handle the file.
  2. Second Msbuild Error occurred(the first vmxxx one caused that) showing that copy the same dll file from one direction to another it's not possible due to System lock (4).

Both two vmxxx processes kept one dll file during build on docker. It was visible in tool "Process Explorer"(use full version from Sysinternals) One vmxxx had lower number of PID which lock the dll file and do not release it before second process with higher number of PID tries do something with it. And it's one random dll file(s) that is kept by two different process.

Also, using and defining only one CPU without parallel on msbuild did not solved the issue before. Same on docker where you are able to manage the cpu and memory. In the end isolation on docker solved the case.

Isolation should take care of processes when you build project from docker container.

user_175228150
Related