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
Open that directory with "Open Folder in Container..." and select Go which is prepared.
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 except remote development extensions.
Failed: Starting the development container
Command failed: C:\Program Files\Docker\Docker\Resources\bin\docker.exe run -a STDOUT -a STDERR --mount type=bind,source=c:\working\hoge,target=/workspaces/hoge -v /host_mnt/c/Users/shishi/.gitconfig:/root/.gitconfig -l vsch.quality=stable -l vsch.local.folder=c:\working\hoge -l vsch.remote.devPort=0 --cap-add=SYS_PTRACE --security-opt seccomp=unconfined vsc-hoge-048b1d910ea70a0935ec782664b5da46 /bin/sh -c echo Container started ; while sleep 1; do :; done
If I put .gitconfig file in home, occur above error.
If I don't put .gitconfig, VS Code makes .gitconfig directory and mount.
If already put .gitconfig directory, VS Code mount that directory.
This behavior doesn't allow to use my .gitconfig file and make a strange directory.
The text was updated successfully, but these errors were encountered:
Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for existing issues here. See also our issue reporting guidelines.
Steps to Reproduce:
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 except remote development extensions.
If I put .gitconfig file in home, occur above error.
If I don't put .gitconfig, VS Code makes .gitconfig directory and mount.
If already put .gitconfig directory, VS Code mount that directory.
This behavior doesn't allow to use my .gitconfig file and make a strange directory.
The text was updated successfully, but these errors were encountered: