-
Notifications
You must be signed in to change notification settings - Fork 275
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
Manual Port Forwarding on Rancher Desktop Networking #4096
Comments
@gunamata @sunilarjun please make sure we include this limitation in the release notes, furthermore, this will change in the upcoming release. |
Thanks @Nino-K . Tagging @jandubois as he writes the release notes. |
@Nino-K Is |
The |
Oh, I see, I missed the Maybe it would be better to tell people to use |
Oh, I didn't think about that, I will test and see if it works. If that works, that would be much better. |
Once the attached PR is merged in, when the new networking is enabled you can use the following commands to expose and unexposed the ports. expose:
unexpose:
|
During the experimental release of RD Networking, the port forwarding has to be performed manually. This is due to the privileged escalation (firewall prompt) that is required by the
host-switch.exe
. It is important to note that this will improve in the upcoming release and the manual step is no longer expected from our users.When port forwarding is needed for e.g:
In order to access the container via the exposed port manual step must be performed.
From WSL VM:
Expose the desired port:
To Unxpose:
Related to: #3810
The text was updated successfully, but these errors were encountered: