[docker ouside of docker] Changing the workspace to ${localWorkspaceFolder} on windows VS Code/Dev Containers does not call a workspace selector window

[hellt]

Hi all,
While doing this in the devcontainer.json on macOS works great:

    "workspaceFolder": "${localWorkspaceFolder}",
    "workspaceMount": "source=${localWorkspaceFolder},target=${localWorkspaceFolder},type=bind"

It does not work on windows 11 and vscode. Trying to run a devcontainer with this config does not open up a window with the workspace selection like it does on macOS, and instead the devcontainer build fails with invalid mount error calling out the workspace dir does not exist.

Is this a known issue?

[devarmenchik1408]

e8ecc9465a872bc1d576932c5b471858a914db06

[devarmenchik1408]

https://ok.ru/profile/559147428212

[chrmarti]

Please append the Dev Containers log from when this happens. (F1 > Dev Containers: Show Container Log)

I guess you had a multi-root workspace open on macOS to get the picker. ${localWorkspaceFolder} does not show a picker.

The problem on Windows might be that you use ${localWorkspaceFolder} as the target folder which needs to be a Linux path, but in this case is a Windows path.

[hellt]

@chrmarti yes, I am using the docker-outside-of-docker feature and follow the provided recommendations to enable the binds.

When using the devcontainer on macOS (using the OrbStack as the docker engine provider) when I first launch the devcontainer I get a picker to select the workspace, and the picker uses the paths of the Linux VM.

On windows we do not get this picker, and judging by your comment it might be expected due to the Windows path elements?

[chrmarti]

Could you append a screenshot of the picker? I think it's the workspace picker for multi-root workspaces, the screenshot would allow to confirm this.

[hellt]

I struggle to invoke the same picker again locally... It appears only when running docker outside of docker with codespaces