Vscode-remote-release: OS X- After upgrading to Docker Desktop 3.0.0, I am no longer able to mount my workspace.

[mxdmedia]

After updating Docker Desktop to 3.0.0, I am no longer able to mount/bind my workspace directory in the running container, and thus re-opening in container fails. This is true of both existing projects which have worked fine for the last year, as well as any new containerized projects I try to create. Looking at the log files after it fails and I reopen locally, I see the following:

[1011 ms] Start: Run: docker run -a STDOUT -a STDERR --mount type=bind,source=/Users/mark/Desktop/PythonProject,target=/workspaces/PythonProject,consistency=delegated -l vsch.quality=stable -l vsch.remote.devPort=0 -l vsch.local.folder=/Users/mark/Desktop/PythonProject --entrypoint /bin/sh vsc-pythonproject-7befea169a39f02c4feed6c81be5fbf4 -c echo Container started ; trap "exit 0" 15; while sleep 1 & wait $!; do :; done
docker: Error response from daemon: invalid mount config for type "bind": bind source path does not exist: /host_mnt/Users/mark/Desktop/PythonProject.

However, the PythonProject directory most certainly does exist (It is the directory open in VSCode). In my Docker Desktop settings, I do have /Users as one of the directories (and their subdirectories) which can be bind mounted into Docker Containers.

Additionally, I added "Docker" to the list of apps in the OS X Settings --> Security & Privacy --> Full Disk Access.

Has anyone seen this, or have any ideas on how to fix it?

REQUESTED DETAILS:

• VSCode Version: 1.51.1
• Local OS Version: OS X Mojave 10.14.6
• Remote OS Version: N/A
• Remote Extension/Connection Type: Docker

Steps to Reproduce:

1. Update docker desktop to 3.0.0
2. Create a directory.
3. Open said directory in VSCode
4. Remote Containers: Add Development Container Configuration Files...
5. Click Show All Definitions --> Python 3 --> 3.8 --> uncheck node --> Click OK
6. Reopen in container

Does this issue occur when you try this locally?: N/A - Remote Container Specific, cant be tried locally.
Does this issue occur when you try this locally and all extensions are disabled?: Remote Container Specific, cant be tried locally.

[mxdmedia]

A quick follow up- it definitely has to do with updating. I just downgraded from 3.0.0 to 2.5.0.1 and I am back up and running again. For anyone running into this issue that (like me) needs to get up and running ASAP, you can simply download docker 2.5.0.1 here: https://desktop.docker.com/mac/stable/49550/Docker.dmg to get back up and running. (Note- the download link for 2.5.0.1 is broken on the docker releases page). VSCode maintainers- feel free to nuke this issue, however it might mean that volumes need to be bound differently in the latest version of docker.

[mxdmedia]

One more followup. Looks like this is a pretty widespread issue with 3.0.0 and OS X. Two fixes are to downgrade to 2.5.0.1 as I did, or disable gRPC in Docker Desktop --> Preferences --> Experimental Features. See this issue over at the docker repo: https://github.com/docker/for-mac/issues/5115

[glimmbo]

Disabling gRPC worked for me! Thank you sir. @mxdmedia