Port forwarding not working as expected

Actual Behavior

Self built images don’t open ports when run with nerdctl run -p 127.0.0.1:8081:80 f2d889a1bc4c. Prebuilt nginx container opens up port 8080 as expected when run with nerdctl run -d -p 127.0.0.1:8080:80 nginx:alpine.

lima.ha.stderr.log shows no error, but also shows no success unlike for nginx image which results in: "level":"debug","msg":"guest agent event: {Time:2022-02-17 15:20:26.158725448 +0000 UTC LocalPortsAdded:[{IP:127.0.0.1 Port:8080}] LocalPortsRemoved:[] Errors:[]}","time":"2022-02-17T16:20:26+01:00"

Steps to Reproduce

Run nerdctl run -p 127.0.0.1:8081:80 f2d889a1bc4c with an image that should react on port 80. Try to telnet into port

Result

Connection not possible on chosen port

Expected Behavior

Connection pssible on exposed port

Additional Information

No response

Rancher Desktop Version

1.0.1

Rancher Desktop K8s Version

1.23.3

Which container runtime are you using?

containerd (nerdctl)

What operating system are you using?

macOS

Operating System / Build Version

macOS Monterey 12.01

What CPU architecture are you using?

arm64 (Apple Silicon)

Linux only: what package format did you use to install Rancher Desktop?

No response

Windows User Only

No response

[danieldonoghue]

I the same issue; I am using Mac m1, moby/dockerd and have exposed the relevant ports in my Dockerfile and published when running but if I attempt to send anything to those ports, I get connection refused…

on the host:

% docker ps|grep cont
ef25e8e3f392   dd-image                "/entrypoint.sh"         36 minutes ago   Up 36 minutes (healthy)   0.0.0.0:16384->16384/udp, :::16384->16384/udp   dd-container

on the container:

% docker exec -it dd-container /bin/bash
bash-5.1# ifconfig eth0
eth0      Link encap:Ethernet  HWaddr 02:42:AC:11:00:02
          inet addr:172.17.0.2  Bcast:172.17.255.255  Mask:255.255.0.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:104 errors:0 dropped:0 overruns:0 frame:0
          TX packets:110 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:6578 (6.4 KiB)  TX bytes:6547 (6.3 KiB)
bash-5.1# nc -l -u -p 16384 -s 0.0.0.0 -v
listening on 0.0.0.0:16384 ...

on the host:

% cat /tmp/test|nc -u 127.0.0.1 16384
read(net): Connection refused

digging further, I see the port is configured in the DOCKER iptables chain on lima…

lima-rancher-desktop:/Users/danield$ sudo iptables -L DOCKER
Chain DOCKER (3 references)
target     prot opt source               destination
ACCEPT     udp  --  anywhere             172.17.0.2           udp dpt:16384

[gunamata]

The problem reported in the issue description seems to have been sorted out. Closing the issue. Please free to reopen if it’s still a problem.