ESOCKETTIMEDOUT and no outgoing network access in workflow

[vemundeldegard]

Hello,

We are working to adopt self hosted runners in our organizations as we are starting to use up the free minutes. I have spent my day trying to overcome various problems, in addition to experiencing Github Actions downtime today.

The current issue I have is no network access in the runner workflow. The yarn command fails, but checking out the Github repository works fine. Both the docker and runner container have access to yarn. I experience this with the workflow failing after some time with the following logs. After failing, the runner pod is terminated. We are using AWS EKS.

yarn install v1.22.19
[1/4] Resolving packages...
[2/4] Fetching packages...
info There appears to be trouble with your network connection. Retrying...
info There appears to be trouble with your network connection. Retrying...
info There appears to be trouble with your network connection. Retrying...
info There appears to be trouble with your network connection. Retrying...
error An unexpected error occurred: "https://registry.yarnpkg.com/@tabler/icons-react/-/icons-react-2.12.0.tgz: ESOCKETTIMEDOUT".

In the Docker container:

/ # ping google.com
PING google.com (172.253.116.102): 56 data bytes
64 bytes from 172.253.116.102: seq=0 ttl=50 time=2.023 ms
64 bytes from 172.253.116.102: seq=1 ttl=50 time=1.564 ms
64 bytes from 172.253.116.102: seq=2 ttl=50 time=1.573 ms
64 bytes from 172.253.116.102: seq=3 ttl=50 time=1.540 ms
--- google.com ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 1.540/1.675/2.023 ms

In the runner container:

PING google.com (209.85.203.102) 56(84) bytes of data.
64 bytes from dh-in-f102.1e100.net (209.85.203.102): icmp_seq=1 ttl=101 time=1.92 ms
64 bytes from dh-in-f102.1e100.net (209.85.203.102): icmp_seq=2 ttl=101 time=1.33 ms
64 bytes from dh-in-f102.1e100.net (209.85.203.102): icmp_seq=3 ttl=101 time=1.32 ms
--- google.com ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2002ms
rtt min/avg/max/mdev = 1.320/1.522/1.921/0.281 ms

I've tested checking the MTU Value, and it is 1500 so it should be correct according to troubleshoots article.

ip link in runner container

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
3: eth0@if6: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9001 qdisc noqueue state UP mode DEFAULT group default 
    link/ether 8e:25:29:0e:82:14 brd ff:ff:ff:ff:ff:ff link-netnsid 0
4: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default 
    link/ether 02:42:f1:e6:62:18 brd ff:ff:ff:ff:ff:ff

ip link in docker container

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
3: eth0@if6: <BROADCAST,MULTICAST,UP,LOWER_UP,M-DOWN> mtu 9001 qdisc noqueue state UP 
    link/ether 8e:25:29:0e:82:14 brd ff:ff:ff:ff:ff:ff
4: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN 
    link/ether 02:42:f1:e6:62:18 brd ff:ff:ff:ff:ff:ff

[ncontrerasj]

hi @vemundeldegard, did you solve this? I'm having the same issue