-
Notifications
You must be signed in to change notification settings - Fork 122
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
Comments
Thanks @j0ju, for connecting these issues! |
This is affecting all of my users on The most frustrating part, for me at least, is that
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. |
Link another issue for feature that vanished from 2.3.0.x series - openvswitch #4660 |
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 |
Issues go stale after 90 days of inactivity. Prevent issues from auto-closing with an 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. |
Closed issues are locked after 30 days of inactivity. 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. |
As of Docker Desktop 2.5, we are up to date with upstream LinuxKit. |
What happened to
# ls /root/lib/modules/4.19.76-linuxkit/extra wireguard.ko
?We were hoping to depend on it being there!
The text was updated successfully, but these errors were encountered: