You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using Windows paths in workspaceMount and workspaceFolder doesn't seem to be possible. Trying to use Windows paths as targets for either volumes and bind mounts will return Workspace folder in devcontainer.json must be an absolute path..
Information
VSCode Version: 1.55.0-insider
Local OS Version: Windows 10
Remote OS Version: Any Windows Container
Remote Extension/Connection Type: Docker
Steps to Reproduce
On a Windows 10 computer, enable Windows Containers.
Check if Windows Containers are working correctly, e.g: docker run -it -v c:\Users\<my-user>:c:\Workspace mcr.microsoft.com/windows/servercore:1809 Powershell
Try to configure .devcontainer/.devcontainer.json:
FROM mcr.microsoft.com/windows/servercore:1809
SHELL ["Powershell", "-Command"]
I have tried a few path variations such as \\, as well as using Unix paths (/), but none would work.
Does this issue occur when you try this locally?: Yes
Does this issue occur when you try this locally and all extensions are disabled?: Yes
The text was updated successfully, but these errors were encountered:
CarlosDomingues
changed the title
workspaceMount/workspaceMount does not support Windows paths
workspaceMount/workspaceMount does not support Windows paths (Windows Containers issue)
Mar 12, 2021
Problem
Using Windows paths in
workspaceMount
andworkspaceFolder
doesn't seem to be possible. Trying to use Windows paths as targets for either volumes and bind mounts will returnWorkspace folder in devcontainer.json must be an absolute path.
.Information
Steps to Reproduce
docker run -it -v c:\Users\<my-user>:c:\Workspace mcr.microsoft.com/windows/servercore:1809 Powershell
.devcontainer/.devcontainer.json
:.devcontainer/Dockerfile
:I have tried a few path variations such as
\\
, as well as using Unix paths (/
), but none would work.Does this issue occur when you try this locally?: Yes
Does this issue occur when you try this locally and all extensions are disabled?: Yes
The text was updated successfully, but these errors were encountered: