Self Hosted Gitea and act_runner running same box #320

New Issue

gritty.map3081 · 2023-08-02T11:53:38Z

gritty.map3081 commented

2023-08-02 11:53:38 +00:00

Hey,
I'm trying to run Gitea and act_runner on the same machine and trying to follow this example of how to use the action:
https://www.alexedwards.net/blog/ci-with-go-and-github-actions

I followed it and I keep getting an error when it gets to the uses: actions/setup-go@v2.

git(version:v0.2.4) received task 10 of job 10, be triggered by event: push
workflow prepared
evaluating expression 'success()'
expression 'success()' evaluated to 'true'
☁ git clone 'https://gitea.domainz.dev/actions/checkout' # ref=v3
cloning https://gitea.domainz.dev/actions/checkout to /root/.cache/act/actions-checkout@v3
Unable to clone https://gitea.domainz.dev/actions/checkout refs/heads/v3: repository not found
repository not found
skipping post step for 'Set up Go'; step was not executed
skipping post step for 'actions/checkout@v3'; step was not executed
Cleaning up services for job audit
Cleaning up container for job audit
🏁 Job failed
repository not found

I don't have actions/checkout or anything in that location ? should I?

Hey, I'm trying to run Gitea and act_runner on the same machine and trying to follow this example of how to use the action: https://www.alexedwards.net/blog/ci-with-go-and-github-actions I followed it and I keep getting an error when it gets to the uses: actions/setup-go@v2. git(version:v0.2.4) received task 10 of job 10, be triggered by event: push workflow prepared evaluating expression 'success()' expression 'success()' evaluated to 'true' ☁ git clone 'https://gitea.domainz.dev/actions/checkout' # ref=v3 cloning https://gitea.domainz.dev/actions/checkout to /root/.cache/act/actions-checkout@v3 Unable to clone https://gitea.domainz.dev/actions/checkout refs/heads/v3: repository not found repository not found skipping post step for 'Set up Go'; step was not executed skipping post step for 'actions/checkout@v3'; step was not executed Cleaning up services for job audit Cleaning up container for job audit 🏁 Job failed repository not found I don't have actions/checkout or anything in that location ? should I?

sillyguodong commented

2023-08-03 03:07:02 +00:00

https://docs.gitea.com/next/administration/config-cheat-sheet#actions-actions
Are you set DEFAULT_ACTIONS_URL set to self?

https://docs.gitea.com/next/administration/config-cheat-sheet#actions-actions Are you set `DEFAULT_ACTIONS_URL` set to `self`?

gritty.map3081 commented

2023-08-03 13:07:58 +00:00

Yes, I did.

I then tried to mirror the repo too. That didn't worth ?

Yes, I did. I then tried to mirror the repo too. That didn't worth ?

wolfogre commented

2023-08-04 02:57:09 +00:00

If you don't have any special needs, I suggest not changing DEFAULT_ACTIONS_URL to self, just leave it empty. Or you have to do some extra work, such as mirroring the repo and making sure it's public.

If you don't have any special needs, I suggest not changing `DEFAULT_ACTIONS_URL` to `self`, just leave it empty. Or you have to do some extra work, such as mirroring the repo and making sure it's public.

nodiscc commented

2023-10-19 21:34:28 +00:00

Unable to clone https://gitea.domainz.dev/actions/checkout refs/heads/v3: repository not found

Is the workflow able to resolve the IP address for gitea.domainz.dev? What is the output if you add these steps before the checkout step?

  - name: test DNS resolution
    run: getent hosts gitea.domainz.dev
  - name: test HTTP request against gitea.domainz.dev
    run: curl -v https://gitea.domainz.dev

Are your workflows running in Docker? If so you should add options: --add-host=gitea.domainz.dev:host-gateway to your act runner configureation file like I did here. This ways containers run by act-runner will use the docker bridge address to access the gitea instance.

For reference, the ansible role I linked above gives a working act-runner setup with the gitea instance running on the same host.

> ` Unable to clone https://gitea.domainz.dev/actions/checkout refs/heads/v3: repository not found` Is the workflow able to resolve the IP address for `gitea.domainz.dev`? What is the output if you add these steps before the checkout step? ```yaml - name: test DNS resolution run: getent hosts gitea.domainz.dev - name: test HTTP request against gitea.domainz.dev run: curl -v https://gitea.domainz.dev ``` Are your workflows running in Docker? If so you should add `options: --add-host=gitea.domainz.dev:host-gateway` to your act runner configureation file like I did [here](https://github.com/nodiscc/xsrv/blob/master/roles/gitea_act_runner/templates/etc_act-runner_config.yaml.j2#L61). This ways containers run by act-runner will use the docker bridge address to access the gitea instance. For reference, the ansible role I linked above gives a working act-runner setup with the gitea instance running on the same host.

Sign in to join this conversation.

No Milestone

No Assignees

4 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: gitea/act_runner#320