Action Runner fails to resolve local address #12473

New Issue

GiteaMirror · 2025-11-02T10:10:58-06:00

GiteaMirror commented

2025-11-02 10:10:58 -06:00

Originally created by @crone66 on GitHub (Feb 12, 2024).

Description

Setup

gitea is running on device A. (host: a.local)
act runner is running on device B. (host: b.local)

Issue

Part of my workflow is the action upload artifact. During the upload I get the following error message

An error has been caught http-client index 0, retrying the upload
Error: getaddrinfo ENOTFOUND a.local
    at GetAddrInfoReqWrap.onlookup [as oncomplete] (node:dns:109:26) {
  errno: -3008,
  code: 'ENOTFOUND',
  syscall: 'getaddrinfo',
  hostname: 'a.local'

Troubleshooting

Initially I registered the runner by using the address a.local during registration. I tried re-registered the runner with the ip address instead but that didn't resolve the issue. Since the runner shouldn't know about a.local after re-registration with the ip my guess is that gitea somehow provides an upload url that contains the dns name and not the ip address.

On device b (act runner) I added the following to the hosts file but that didn't help.

192.168.178.21 a.local

Gitea Version

1.21.4

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Screenshots

No response

Git Version

No response

Operating System

Synolgy 7.1.1

How are you running Gitea?

Gitea from SynoCommunity ->https://github.com/wkobiela

Database

MySQL/MariaDB

Originally created by @crone66 on GitHub (Feb 12, 2024). ### Description ### Setup gitea is running on device A. (host: a.local) act runner is running on device B. (host: b.local) ### Issue Part of my workflow is the action upload artifact. During the upload I get the following error message ``` An error has been caught http-client index 0, retrying the upload Error: getaddrinfo ENOTFOUND a.local at GetAddrInfoReqWrap.onlookup [as oncomplete] (node:dns:109:26) { errno: -3008, code: 'ENOTFOUND', syscall: 'getaddrinfo', hostname: 'a.local' ``` ### Troubleshooting Initially I registered the runner by using the address a.local during registration. I tried re-registered the runner with the ip address instead but that didn't resolve the issue. Since the runner shouldn't know about a.local after re-registration with the ip my guess is that gitea somehow provides an upload url that contains the dns name and not the ip address. On device b (act runner) I added the following to the hosts file but that didn't help. `192.168.178.21 a.local` ### Gitea Version 1.21.4 ### Can you reproduce the bug on the Gitea demo site? No ### Log Gist _No response_ ### Screenshots _No response_ ### Git Version _No response_ ### Operating System Synolgy 7.1.1 ### How are you running Gitea? Gitea from SynoCommunity ->https://github.com/wkobiela ### Database MySQL/MariaDB

GiteaMirror added the topic/gitea-actions type/bug labels 2025-11-02 10:10:58 -06:00

GiteaMirror commented

2025-11-02 10:10:58 -06:00

@KN4CK3R commented on GitHub (Feb 12, 2024):

You could debug your network config with some ping action steps. I'm sure this is not a Gitea/Runner problem.

@KN4CK3R commented on GitHub (Feb 12, 2024): You could debug your network config with some `ping ` action steps. I'm sure this is not a Gitea/Runner problem.

GiteaMirror commented

2025-11-02 10:10:59 -06:00

@crone66 commented on GitHub (Feb 13, 2024):

I know that I can reach the destination since I do a checkout from gittea (a.local) before I try to upload the artifacts. Therefore, I'm confused why the checkout works and why the runner uses the hostname instead of the IP to upload the artifact. Besides that I have no special network configuration I just specified the hostnames of the devices. No lan firewalls, subnets or something like that is used.

The only thing that I could change would be to remove the hostname from a.local since this should effectively force the runner to use the IP address. But this solution is not great since I have to reconfigure all devices in the network.

@crone66 commented on GitHub (Feb 13, 2024): I know that I can reach the destination since I do a checkout from gittea (a.local) before I try to upload the artifacts. Therefore, I'm confused why the checkout works and why the runner uses the hostname instead of the IP to upload the artifact. Besides that I have no special network configuration I just specified the hostnames of the devices. No lan firewalls, subnets or something like that is used. The only thing that I could change would be to remove the hostname from a.local since this should effectively force the runner to use the IP address. But this solution is not great since I have to reconfigure all devices in the network.

GiteaMirror commented

2025-11-02 10:10:59 -06:00

@yp05327 commented on GitHub (Mar 22, 2024):

Did you use a config file to start the runner? You can adjust the job container's network settings.

@yp05327 commented on GitHub (Mar 22, 2024): Did you use a config file to start the runner? You can adjust the job container's network settings. ![image](https://github.com/go-gitea/gitea/assets/18380374/e5f154f9-a3b8-432a-93aa-137c2538707d)

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#12473