You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Ping step's purpose is to check that the dns setting is correctly applied. It return the following which is expected given the defined DNS server in this context (this server is used to return local IPs intead of public ones for the domain ar2000.me.
* Trying 192.168.1.15:443...
* Connected to gitea.ar2000.me (192.168.1.15) port 443 (#0)
*
Registry hostname are wrong on purpose to generate errors logs. The step Login into image repo using docker/login-action clearly show the wrong DNS server in it's error (8.8.8.8, should be 192.168.1.15)
Logging into gitea:3000...
::error::Error response from daemon: Get "https://gitea:3000/v2/": dial tcp: lookup gitea on 8.8.8.8:53: no such host
Test have been run on a self hosted gitea v1.22.2 instance with the runner container gitea/act_runner
The text was updated successfully, but these errors were encountered:
Tools like docker/login-action and docker/build-push-action do not use the runner dns and hosts files.
Step to reproduce :
Example workflow :
The
Ping
step's purpose is to check that the dns setting is correctly applied. It return the following which is expected given the defined DNS server in this context (this server is used to return local IPs intead of public ones for the domainar2000.me
.Registry hostname are wrong on purpose to generate errors logs. The step
Login into image repo
using docker/login-action clearly show the wrong DNS server in it's error (8.8.8.8
, should be192.168.1.15
)Test have been run on a self hosted gitea v1.22.2 instance with the runner container gitea/act_runner
The text was updated successfully, but these errors were encountered: