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

Might include that WSL1 is not compatible with Ubuntu20.04 #662

Closed
MaxPowerWasTaken opened this issue May 6, 2020 — with docs.microsoft.com · 4 comments
Closed

Comments

Copy link

Setting up WSL, when I reached "Install your Linux Distribution of Choice" I went with the latest Ubuntu LTS - 20.04. After running into [this issue[(https://github.com/microsoft/WSL/issues/5125) trying to run apt-key add, I was pointed to this warning that Ubuntu 20.04 is not yet compatible with WSL1.

I think this would be helpful to have highlighted in this install instructions page, as absent this warning, I think many people would probably assume choosing the latest LTS Ubuntu is a safe distro choice.


Document Details

Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

Copy link

pechter commented May 7, 2020

WSL2 has some serious advantages over WSL1. However, WSL2 doesn't coexist with VMware Player/Workstation or VirtualBox unless you have a fairly new cpu on the box. VMware's betaing a version that works with the new Device Guard... The dual 6 core Xeons on the box here used for testing has to have WSL2 removed to test the same thing in Windows Subsystem for Linux. Ugh.

@cgaolei
Copy link

cgaolei commented May 7, 2020

Having this problem when adding apt-key add in 20.04LTS Sublinux system:

gpg: can't connect to the agent: IPC connect call failed

Copy link

ghost commented May 11, 2020

i removed gpg and installed gnupg1, and it worked...

$sudo apt-get remove gpg
$sudo apt-get install gnupg1

@MaxPowerWasTaken
Copy link
Author

Interesting - thanks zico. Would you be willing to post that workaround on the ubuntu forum and MS/WSL github issue page I linked above? I'd be interested to see if the maintainers there agree that workaround is 'safe'. But sounds awesome, thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants