-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Complete WSL implementation in Podman 5 #21597
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: n1hility The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/hold |
Ephemeral COPR build failed. @containers/packit-build please check. |
64da6b4
to
ca7c087
Compare
the stop failure is legit problem ... |
@n1hility this patch resolves the test problem. My only pause is I am not dead sure if I am treating a symptom instead of fixing the real problem. But on that front, I do not see something like a missed .Close() ... maybe take a quick peek before applying my patch. The patch also explains whats going on where the cause/effect? is ... maybe someone else will see it too.
|
Signed-off-by: Brent Baude <[email protected]>
Also addresses a number of issues: - StopHostNetworking isn't plumbed, win-sshproxy leaks on hyperv - Wait api and print output doesn't work properly on Windows - API forwarding doesn't work on WSL - Terminal corruption with after start/stop on Windows - Gvproxy is forcefully killed vs gracefully quit - Switching rootful/rootless does not update /var/run/docker.sock on the guest - File already closed error on init - HyperV backend is publishing Unix sockets when it should be named pipes - User-mode networking doesn't always work - Stop state outside of lock boundaries - WSL blocks parallel machined (should be supported) [NO NEW TESTS NEEDED] Signed-off-by: Jason T. Greene <[email protected]>
ca7c087
to
97025ea
Compare
@baude thanks! I applied your patch and rebased again. i mentioned in chat but just in case you miss it that i noticed some underlying raciness in qemu start/stop that we can fixup later (e.g. the logic has the netdev sock setup overwriting the qmp monitor sock which confuse client connection code) |
cffb9d0
to
10cf59b
Compare
Improve error reporting on ssh readiness check Signed-off-by: Jason T. Greene <[email protected]>
Signed-off-by: Jason T. Greene <[email protected]>
10cf59b
to
bb7d8fd
Compare
LGTM |
@n1hility regarding this comment #21597 (comment) Why don't just eliminate the root cause and don't reuse QMP for VLAN in QEMU. It is what I proposed in #21594 with a bigger change. But this could be also achieved w/o removing this FD. Just use dedicated socket for the purpose. |
LGTM other than the prev reviews. |
Signed-off-by: Jason T. Greene <[email protected]>
I totally agree we need to fix this, and soon, but I also don't want this PR to grow beyond what it is (already pretty huge) and its holding up WSL working in 5. That and other stuff can come in other commits. |
I added the small comment review charge in a separate commit to address the review, yet still show the record of CI passing on the earlier commits. |
i think there is consensus to get this PR in after @n1hility addressed the first round of comments ... /hold |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM but for the size it is hard to properly review so it is hard to catch things.
Looks like windows CI is still disabled, does that mean we can turn it on after this merges?
/hold cancel |
c524da2
into
containers:main
Complete WSL implementation, refactor a few areas
Also addresses a number of issues:
- StopHostNetworking isn't plumbed, win-sshproxy leaks on hyperv
- Wait api and print output doesn't work properly on Windows
- API forwarding doesn't work on WSL
- Terminal corruption with after start/stop on Windows
- Gvproxy is forcefully killed vs gracefully quit
- Switching rootful/rootless does not update /var/run/docker.sock on the guest
- File already closed error on init
- HyperV backend is publishing Unix sockets when it should be named pipes
- User-mode networking doesn't always work
- Stop state outside of lock boundaries
- WSL blocks parallel machined (should be supported)