My Situation #

I'm a Stack Overflow user currently running Docker Desktop Edge. Previously, I fixed an "Unknown reason for drive sharing failure" issue by switching to the Edge version, but now a new problem has popped up: 3 out of 4 containers fail to build. These containers have been tested and run successfully on multiple other systems, and all failing containers throw the same core error:

ERROR: for db Cannot create container for service db: status code not OK but 500: {"Message":"Unhandled exception: Filesharing has been cancelled"}
Encountered errors while bringing up the project.

Full Error Log #

Creating imt2291-part2_www_1 ... 
Creating imt2291-part2_phpmyadmin_1 ... done
Creating imt2291-part2_db_1 ... 
Creating imt2291-part2_test_1 ... error
Creating imt2291-part2_www_1 ... error
ERROR: for imt2291-part2_test_1 Cannot create container for service test: status code not OK but 500: {"Message":"Unhandled exception: Filesharing has been cancelled"}
ERROR: for imt2291-part2_www_1 Cannot create container for service www: status 
Creating imt2291-part2_db_1 ... error lled"}
ERROR: for imt2291-part2_db_1 Cannot create container for service db: status code not OK but 500: {"Message":"Unhandled exception: Filesharing has been cancelled"}
ERROR: for test Cannot create container for service test: status code not OK but 500: {"Message":"Unhandled exception: Filesharing has been cancelled"}
ERROR: for www Cannot create container for service www: status code not OK but 500: {"Message":"Unhandled exception: Filesharing has been cancelled"}
ERROR: for db Cannot create container for service db: status code not OK but 500: {"Message":"Unhandled exception: Filesharing has been cancelled"}
Encountered errors while bringing up the project.

Question #

Has anyone encountered this issue and found a solution?

Expert Answer #

Hey there, I’ve dealt with this exact headache using Docker Desktop Edge before, and here are several fixes that worked for me and other developers in the community:

• Recheck drive sharing permissions: Even if you enabled them earlier, Edge builds sometimes reset these settings. Head to Docker Desktop Settings → Resources → File Sharing, confirm the drive hosting your project is checked. Toggle it off, apply, then toggle it back on and restart Docker Desktop fully.
• Factory reset Docker Desktop: This clears up wonky state issues from the Edge update. Go to Settings → Troubleshoot → Reset to factory defaults. Just remember to back up any critical containers or images first!
• Rule out antivirus interference: Windows Defender or third-party security tools often block Docker’s file sharing. Temporarily disable real-time protection (only for testing purposes!) and try building again. If it works, add Docker’s processes or your project folder to the antivirus exceptions list.
• Clean reinstall the latest Edge build: Sometimes the initial install gets corrupted. Uninstall Docker Desktop, restart your machine, then download the latest Edge version and do a fresh install.
• Validate your docker-compose.yml mounts: Ensure your volume paths are correct—Windows case sensitivity can trip up Edge builds more than stable ones. Avoid special characters in paths, and double-check that local folders (like ./src) exist as expected.

A quick note: Edge builds are experimental by nature, so bugs like this aren’t uncommon. If none of these fixes work, rolling back to the latest stable Docker Desktop version might be a reliable temporary workaround until this issue is patched.

内容的提问来源于stack exchange，提问作者infroz