-
-
Notifications
You must be signed in to change notification settings - Fork 39
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
Doesn't work in Win11 #13
Comments
Can you re-run the installation using a fresh copy of the install.ps1 script (I've just pushed some changes)? The files as of now should wait for systemd more reliably so that you aren't logged into the namespace "too early", which is likely the issue here. There is another issue with the GPG support in that it only works in the first shell you open after restarting the distro. I haven't worked out why it fails on subsequent launches yet. |
🎉 |
Right, while this works, actually I have problems with Docker and SSH now.
Docker just doesn't detect that it's running, although integration is enabled in the settings:
Any idea what causes this? |
Quick update - I've reset Ubuntu and tried again on a clean system. |
After shutting down with
Error arrives again after closing the current tab and opening a new one. As for the Docker - it warns that it was shut down, restarts, but doesn't work with the same So yeah, so far it works unreliably. |
thanks for the updates. I've seen this behaviour of ssh-agent and gpg-agents both failing in subsequent sessions where they work fine in the very first session. I'm unsure what's up but I think it's something to do with the WSL interop feature not allowing cross-session calls - i.e. your second session accessing the socat running under the first session, even if you've closed your first session. |
OK, should we create a separate issue for that then? Or just leave it as is here (renaming the title)? |
Anything on this? |
Hi! I'm currently unable to use GPG through the bridge.
Basic install of the script with only
-d Ubuntu
flag (so GPG was installed by the script), fresh Ubuntu install.After restarting WSL, I get the next output:
It partially looks like this error which I got during the previous run under Win10.
The text was updated successfully, but these errors were encountered: