microsoft / microsoft/vscode-remote-release

Devcontainer cloning fails with invalid characters for a local volume name error

Open
#7,396 2 comments 1 reaction 1 assignee View on GitHub

@chrmarti is already working on this.

Since Oct 25, 2022.

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

Description

  • VSCode Version: 1.72.2
  • Local OS Version: Windows_NT x64 10.0.25227
  • Remote OS Version: Docker
  • Remote Extension/Connection Type: Containers
  • Logs:
[140 ms] Start: Check Docker is running
[140 ms] Start: Run: docker version --format {{.Server.APIVersion}}
[1074 ms] Server API version: 1.41
[1076 ms] Start: Run: docker volume ls -q
[1539 ms] Start: Run: docker volume create --label vsch.local.repository=https://github.com/agowa338/.git_mgmt.git/tree/main --label vsch.local.repository.unique=true --label vsch.local.repository.branch=main .git_mgmt-main-81432cc5337c26d3a57b0ddcc532f686
[1971 ms] Command failed: docker volume create --label vsch.local.repository=https://github.com/agowa338/.git_mgmt.git/tree/main --label vsch.local.repository.unique=true --label vsch.local.repository.branch=main .git_mgmt-main-81432cc5337c26d3a57b0ddcc532f686
[1972 ms] Error response from daemon: create .git_mgmt-main-81432cc5337c26d3a57b0ddcc532f686: ".git_mgmt-main-81432cc5337c26d3a57b0ddcc532f686" includes invalid characters for a local volume name, only "[a-zA-Z0-9][a-zA-Z0-9_.-]" are allowed. If you intended to pass a host directory, use absolute path
[1972 ms] Exit code 1

Steps to Reproduce:

  1. Create a git repository with a name starting with either "." or "_" (anything that does NOT match the regex from the error message probably will do [a-zA-Z0-9][a-zA-Z0-9_.-])
  2. Use "Clone Repository in Container Volume"

Does this issue occur when you try this locally?: No
Does this issue occur when you try this locally and all extensions are disabled?: No

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.