https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# rancher-desktop
a
This message was deleted.
f
Did you adjust the privileged port setting to allow user-level processes to bind to port 80?
Copy code
sudo sysctl -w net.ipv4.ip_unprivileged_port_start=80
Rancher Desktop runs as your regular user, not as 
root
, so it can't bind the ingress ports without it
b
@fast-garage-66093 Hi, yes I have that set, now I have multiple network interfaces (1 primary, 2 bridges and 2 unconfigured), could that be an issue?
w
Doesn't Traefik use 80? I had to disable, but my situation was probably different.
b
@white-xylophone-9961 Hi traefix is disabled and removed, then install metallb
And it all appears to be working if I port forward 80 to the localhost as a test... On the host if I run 
ip neigh show dev eno1
it shows 
192.168.10.185 FAILED
f
I'm confused now, isn't 
192.168.10.185
the ip address of your host?
Unless I'm even more confused than usual, there isn't any external network attached to the VM on Linux. All you have is the slirp user-mode network, plus the port forwarding to the host. So any routable IP address would have to be the host IP address.
b
@fast-garage-66093 on MacOS this is possible (as per the demo?), but not Linux, so just port forward to localhost?
f
Yes. On macOS we can create a bridged or shared network adapter via VMNET, but there is nothing implemented for it on Linux yet.
b
@fast-garage-66093 OK, so port forward to localhost then is fine? What about passt (I see that's active)as an alternative?
f
Sorry, I don't follow
b
@fast-garage-66093 following the nginx demo, just port forward. It seems passt is the replacement for slirp?
f
We (both Rancher Desktop and Lima) are looking at using gVisor network tunnelling as the possible replacement for slirp.
Rancher Desktop 1.8.0 has an experimental implementation of it (for Windows only)
b
@fast-garage-66093 ahh ok, looks interesting 🙂 Thanks for your help today 🙂
f
You are welcome!
10 Views
Open in Slack
PreviousNext
Powered by