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

What happened to wireguard kernel module? #4560

Closed
thebalaa opened this issue May 13, 2020 · 8 comments
Closed

What happened to wireguard kernel module? #4560

thebalaa opened this issue May 13, 2020 · 8 comments

Comments

@thebalaa
Copy link

What happened to # ls /root/lib/modules/4.19.76-linuxkit/extra wireguard.ko ?

We were hoping to depend on it being there!

@j0ju
Copy link

j0ju commented May 15, 2020

This is a similiar issue to #4549 and #4552, used features have been vanished from the 2.3.0.x series.
Please include this again.

@thebalaa
Copy link
Author

Thanks @j0ju, for connecting these issues!

@slushie
Copy link

slushie commented May 19, 2020

This is affecting all of my users on 2.3.0.2 (45183). There is no kernel module for WireGuard included in the LinuxKit build for Docker Desktop. Initially, I assumed this was a bug for LinuxKit since there have been changes to the way the WG module is pulled into the kernel tree, but now I believe that is unrelated.

The most frustrating part, for me at least, is that docker version reports the exact same version strings for every component across this upgrade. That makes it really difficult to determine which users are affected. However, it's possible to get the build timestamp for the LinuxKit kernel and that can be used to identify affected users.

$ docker run -ti --net=host  alpine uname -a
Linux docker-desktop 4.19.76-linuxkit #1 SMP Fri Apr 3 15:53:26 UTC 2020 x86_64 Linux

I'm currently recommending that users downgrade to the previous Docker Desktop release due to this and other issues in the latest release. We're waiting for a response from Docker, Inc. before suggesting that users upgrade.

@aharonnovo
Copy link

Link another issue for feature that vanished from 2.3.0.x series - openvswitch #4660

@slushie
Copy link

slushie commented Jun 19, 2020

I've been motivated by the lack of response from Docker, Inc. that I put together my own solution to build kernel modules for Docker VMs. I'm using it now to build the wireguard module for my users. Hopefully it can be useful for you as well!

@docker-robott
Copy link
Collaborator

Issues go stale after 90 days of inactivity.
Mark the issue as fresh with /remove-lifecycle stale comment.
Stale issues will be closed after an additional 30 days of inactivity.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle stale

@docker-robott
Copy link
Collaborator

Closed issues are locked after 30 days of inactivity.
This helps our team focus on active issues.

If you have found a problem that seems similar to this, please open a new issue.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle locked

@docker docker locked and limited conversation to collaborators Nov 16, 2020
@stephen-turner
Copy link
Contributor

As of Docker Desktop 2.5, we are up to date with upstream LinuxKit.

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

No branches or pull requests

6 participants