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
Podman machine user mode networking reset doesn't restore wsl.conf #20625
Comments
@n1hility PTAL |
Thanks for the report this is indeed a bug. Will take a look at it soon. |
/assign |
A somewhat related question on this that just came up. Feel free to ignore or tell me to ask elsewhere if this isn't the place: With user mode networking active, how does one communicate between the podman machine (or a container running on the machine) and the windows host? For example, if I wanted to forward X to an X server running on my Windows machine. With the default networking I can get the windows host IP from Thanks for working on the bug! |
@Narwhalrus If you are using user-mode networking you could always use the IP address 192.168.127.254, which is the internal host. Alternatively with either user-mode / non user-mode you can use your windows host pc / host name with a .local suffix (e.g foo.local). Although for this particular .local name to route correctly (since it points to your external ip), it does require that your local windows defender policy allow it. You may need to add a rule if it does not. |
I'll give that a shot. Thank you for the quick reply! |
Issue Description
When switching between "normal" networking and user mode networking on the WSL2 podman machine, the wsl.conf isn't restored to it's default state, which results in networking issues when communicating from containers to the Windows host.
Steps to reproduce the issue
Steps to reproduce the issue
In powershell...
Describe the results you received
/etc/wsl.conf
is not restored to the default:that is installed with the podman machine
Describe the results you expected
/etc/wsl.conf
is restored to the default when switching from user mode networking to "normal" networkingpodman info output
Podman in a container
No
Privileged Or Rootless
None
Upstream Latest Release
No
Additional environment details
No response
Additional information
Workaround is to manually restore
/etc/wsl.conf
to the original configuration withoutgenerateResolvConf = false
and restart the podman machine.The text was updated successfully, but these errors were encountered: