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
com.docker.backend.exe is locking random files in latest stable release #5624
Comments
|
Most likely related to issues in #5567 |
|
also having this issue while using npm/yarn |
|
We think this has now been fixed in our master branch. Many thanks! |
|
@hardcoremore it’s hard to tell what this is about with just a screenshot, could you explain what you’re doing and upload a diagnostic (Troubleshot window from the systray menu)? |
|
Well I am trying just to delete the file. Both host (windows) and container are telling me that file does not exists. How can I Troubleshot window from the systray menu? |
|
I have uploaded diagnostic. Check it out here: #5985 |
File was created with php inside container. I tried to delete it from host (windows) and file is visible inside explorer but could not be deleted because it says that file could not be found. Also file could not be deleted from inside container as well. It also says that file does not exists. |
|
The original issue in this ticket is fixed in 2.2.0.4. The new issue is unrelated but is now being dealt with in #5985, so I'll close this ticket. |
|
Closed issues are locked after 30 days of inactivity. If you have found a problem that seems similar to this, please open a new issue. Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows. |




Expected behavior
Files not to be randomly locked by docker.
Actual behavior
Random files are being locked.
This script worked fine prior to install of latest stable release:
Information
Windows Version:

Docker Desktop Version:

Are you running inside a virtualized Windows e.g. on a cloud server or on a mac VM: no
Steps to reproduce the behavior
The text was updated successfully, but these errors were encountered: