Debug SAM applications breaks with Docker 2.2.0.0 on VS Code (Windows 10)

[manucohenyashar]

After upgrading to version 2.2.0.0 debugging SAM applications stopped working in ALL runtimes (Python, node, etc). Running the application works but attaching the debugger breaks with the error: "docker.errors.APIError: 500 Server Error: Internal Server Error ("error while creating mount source path '/host_mnt/c/Users/{user name}/AppData/Local/Temp/aws-toolkit-vscode/vsctkDZvlgv/output/awsToolkitSamLocalResource': mkdir /host_mnt/c/Users/{user name}: file exists")"

I disabled the local firewall to make sure no network errors cause the issue. Also, the fact that running the application (sam local invoke) works tells me that mounting works.

• [*] I have tried with the latest version of my channel (Stable or Edge)
• [ *] I have uploaded Diagnostics
• Diagnostics ID: A70E650C-EEE0-423B-A795-55F2DD760CFD/20200123155536

Expected behavior

The debugger should attach (using the default port 5858)

Actual behavior

Attach debugger fails with the error:

docker.errors.APIError: 500 Server Error: Internal Server Error ("error while creating mount source path '/host_mnt/c/Users/{my user name}/AppData/Local/Temp/aws-toolkit-vscode/vsctkDZvlgv/output/awsToolkitSamLocalResource': mkdir /host_mnt/c/Users/{my user name}: file exists")

Information

• Windows Version: Windows 10.0.18362
• Docker Desktop Version: 2.2.0.0
• Are you running inside a virtualized Windows e.g. on a cloud server or on a mac VM: No

Steps to reproduce the behavior

1. Create a new SAM application in VS Code or SAM init, The runtime is not important, the problems happen in ALL runtimes.
2. Click "Debug Locally" (Code lens in VS Code)

[stephen-turner]

Dupe of #5516.

[manucohenyashar]

Issue 5516 does not provide a workaround or a solution when using tools that internally use upper case when mounting, so I think this issue should be reopened.

[stephen-turner]

We will have a fix for #5516, we're not expecting people to rely on the workaround.

[manucohenyashar]

Just got the build (ver 2.2.0.1) which fixed the issue.

[docker-robott]

Closed issues are locked after 30 days of inactivity.
This helps our team focus on active issues.

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.
/lifecycle locked