microsoft / microsoft/vscode-remote-release

Windows: Detect when drive sharing credentials need to be reset

Open
#2,288 1 comment 0 reactions 1 assignee View on GitHub

@chrmarti is already working on this.

Since Feb 3, 2020.

containers feature-request
Dominant language
Dockerfile
Stars
4.2k
Forks
470
Avg merge
1d 1h
Merged PRs (30d)
1

Description

Log might look like:

[1128 ms] Start: Run: git rev-parse --show-toplevel
[1237 ms] Start: Starting container
[1237 ms] Start: Run: docker run -a STDOUT -a STDERR --mount type=bind,source=d:/repos/Microsoft/vscode-dev-containers,target=/workspaces/vscode-dev-containers,consistency=cached -l vsch.quality=insider -l vsch.remote.devPort=0 -l vsch.local.folder=d:\repos\Microsoft\vscode-dev-containers\containers\cpp --cap-add=SYS_PTRACE --security-opt seccomp=unconfined --entrypoint /bin/sh vsc-cpp-f766cf14e075f90f128919a60c7ed189 -c echo Container started ; while sleep 1; do :; done
[1569 ms] 
[2077 ms] C:\Program Files\Docker\Docker\Resources\bin\docker.exe: Error response from daemon: invalid mount config for type "bind": stat /host_mnt/d/repos/Microsoft/vscode-dev-containers: permission denied.
See 'C:\Program Files\Docker\Docker\Resources\bin\docker.exe run --help'.
[2078 ms] Failed: Starting the development container
[2088 ms] Command failed: C:\Program Files\Docker\Docker\Resources\bin\docker.exe run -a STDOUT -a STDERR --mount type=bind,source=d:/repos/Microsoft/vscode-dev-containers,target=/workspaces/vscode-dev-containers,consistency=cached -l vsch.quality=insider -l vsch.remote.devPort=0 -l vsch.local.folder=d:\repos\Microsoft\vscode-dev-containers\containers\cpp --cap-add=SYS_PTRACE --security-opt seccomp=unconfined --entrypoint /bin/sh vsc-cpp-f766cf14e075f90f128919a60c7ed189 -c echo Container started ; while sleep 1; do :; done

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.