microsoft / microsoft/vscode-remote-release

Clone Repository in Container volume throws error when trying to Clone the actuall repository

Open
#7,424 4 comments 0 reactions 1 assignee View on GitHub

@chrmarti is already working on this.

Since Oct 28, 2022.

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

Description

Version: 1.72.2 (user setup)
Commit: d045a5eda657f4d7b676dedbfa7aab8207f8a075
Date: 2022-10-12T22:15:18.074Z (1 wk ago)
Electron: 19.0.17
Chromium: 102.0.5005.167
Node.js: 16.14.2
V8: 10.2.154.15-electron.0
OS: Windows_NT x64 10.0.22621
Sandboxed: No

Steps to Reproduce:

  1. Clone Repository in Container volume
  2. Enter URL https://companyname@dev.azure.com/companyname/Project/_git/Project
  3. Press enter
  4. Click on Starting Dev Contianer (show log)
  5. Wait for it to try and clone the repository
[2075 ms] Start: Run in container: git clone --depth 1 https://companyname@dev.azure.com/companyname/Project/_git/Project.
Cloning into '.'...
fatal: Cannot determine the organization name for this 'dev.azure.com' remote URL. Ensure the `credential.useHttpPath` configuration value is set, or set the organization name as the user in the remote URL '{org
}@dev.azure.com'.
fatal: could not read Password for 'https://companyname@dev.azure.com': terminal prompts disabled
Password for 'https://enumsoftware@dev.azure.com':

similar issue https://github.com/microsoft/vscode-remote-release/issues/2620

As I can see it is trying to pull out a prompt, but he cannot because it is in Docker for Gitlab for example if i am authorized on my computer authorization also works in docker container so i am confused.

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

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.