Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WSL2 Ubuntu 18.04 - Unable to Perform Any Type of Setup #229

Closed
2 of 16 tasks
ryanspletzer opened this issue Nov 22, 2020 · 0 comments · Fixed by #298
Closed
2 of 16 tasks

WSL2 Ubuntu 18.04 - Unable to Perform Any Type of Setup #229

ryanspletzer opened this issue Nov 22, 2020 · 0 comments · Fixed by #298
Labels
platform:wsl Specific to Windows Subsystem for Linux

Comments

@ryanspletzer
Copy link

Which version of GCM Core are you using?

From a terminal, run git-credential-manager-core version and paste the output.

Git Credential Manager version 2.0.280-beta+1f4c6db90f (Linux, .NET Core 3.1.6)

Which Git host provider are you trying to connect to?

  • Azure DevOps
  • Azure DevOps Server (TFS/on-prem)
  • GitHub
  • GitHub Enterprise
  • Bitbucket
  • Other - please describe

Can you access the remote repository directly in the browser using the remote URL?

From a terminal, run git remote -v to see your remote URL.

  • Yes
  • No, I get a permission error
  • No, for a different reason - please describe

[Azure DevOps only] What format is your remote URL?

[Azure DevOps only] If the account picker shows more than one identity as you authenticate, check that you selected the same one that has access on the web.

  • Not applicable
  • I only see one identity
  • I checked each identity and none worked

Expected behavior

I am authenticated and my Git operation completes successfully.

Actual behavior

Following the setup steps for Linux in WSL2 Ubuntu 18.04, I cannot even get the plaintext store to work. I see the following when trying to clone a private repo from github.com. Inputting a PAT does not store the token and ~/.gcm/store is not created. I've had similar issues with the gpg/pass setup. (Tried avoiding gpg for the moment just to see if I could get the simpler plaintext setup in place -- I think something else is going on, though.) I did the setup via the .deb package.

image

Logs

Set the environment variables GCM_TRACE=1 and GIT_TRACE=1 and re-run your Git command. Review and redact any private information and attach the log.

Log is attached.

git.log

@vtbassmatt vtbassmatt added platform:linux Specific to a Linux-based platform platform:wsl Specific to Windows Subsystem for Linux and removed platform:linux Specific to a Linux-based platform labels Feb 11, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
platform:wsl Specific to Windows Subsystem for Linux
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants