Add support for Gitea actions via act_runner. #19
No reviewers
Labels
No Label
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
Copied from Github
Kind/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: cerc-io/hosting#19
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "telackey/act_runner"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This adds an act_runner instance to the docker-compose.
There is no good way to retrieve a token for registering the runner from Gitea at this time, so we seed the DB with one during initialization.
@ -51,0 +61,4 @@
- gitea
volumes:
- /var/run/docker.sock:/var/run/docker.sock
- ./act_runner:/data
For...reasons...we use
gitea.local
rather thanhost.docker.internal
. I forget for the moment exactly those reasons. Possibly because we want the hostname to be usable from the host as well as inside containers. Possibly also we want to be able to target a gitea that is running somewhere other than on the host?@ -51,0 +61,4 @@
- gitea
volumes:
- /var/run/docker.sock:/var/run/docker.sock
- ./act_runner:/data
The GITEA_INSTANCE_URL is used by act_runner for two things: (1) what endpoint to poll for new tasks, (2) for constructing the URL to pass to any spawned task executors for checking out code.
Unfortunately neither
server
(the container name in the stack) norgitea.local
are resolvable for both (1) and (2).server
works for (1) but not (2) (since task containers spawned by act_runner are not in the same SO stack) and gitea.local won't work for either, since it isn't resolvable inside docker.The only name thing I've found that works universally is to reach back to the exposed port on the host.
@ -51,0 +61,4 @@
- gitea
volumes:
- /var/run/docker.sock:/var/run/docker.sock
- ./act_runner:/data
(Note, if we could somehow make sure that any newly spawned task containers were attached to the same stack, we could likely use
server
.)@ -51,0 +61,4 @@
- gitea
volumes:
- /var/run/docker.sock:/var/run/docker.sock
- ./act_runner:/data
Hmm. I thought
host.docker.internal
wasn't defined in all Docker installs?