A more robust way to manage act_runner

[Sharaf5]

Feature Description

I'm running gitea with act_runner from inside docker
it's perfect : until I tried to use replicas to add more runners for workflows to run in paralel as it's only go for jobs one by one and only run one workflow in a time

I ended with this setup that runs 2 replicas with 2 volumes each for data of each container

services:
...
  gitea-act:
    # image: gitea/act_runner:latest-dind-rootless
    image: gitea/act_runner
    # never use wit replicas
    # container_name: gitea-act
    volumes:
      - ./actions/config.yaml:/config.yaml
      - /data
      # - /var/run/docker.sock:/var/run/docker.sock
      - SOC_DOCKER:/var/run/:delegated
    environment:
      - CONFIG_FILE=/config.yaml
      - GITEA_INSTANCE_URL=https://x.x.x.x/
      - GITEA_HTTP_PORT = 80
      # - GITEA_RUNNER_NAME=xxxxx
      # - GITEA_RUNNER_REGISTRATION_TOKEN=xxxxxxxxxxxxxxxxxxxxxxxxxxxx
    networks:
      static:
        ipv4_address: x.x.x.x.
    deploy:
      mode: replicated
      replicas: 2
    depends_on:
      dind:
        condition: service_healthy
      gitea:
        condition: service_started
...

The proplem now is that it doesn't register unless we give it a token
and if so one only will be registed and the other will be rejected

I sugget that runners have some more management like :

• accept automaticly from a range of IPs or interface
• if runner don't have token, put it in pending state and let the UI user to accept it or reject it - may be useful for k8s
• rejected or deleted runners should just delete it's data from database and reject token, rather than blocking the runner itself
• refactor the delete event as block event with options to just block runner or ip runner comes from

Screenshots

No response

[lunny]

What's your Gitea version? I think Gitea supports reusing the register token from 1.21.

[Sharaf5]

1.22 dockerized
the replica only stops without any errors
I'll check agian for the network

[Sharaf5]

Oh I had to use the same local network without one specified ip
turn out the acceptance of the same tocken is not what prevent registeration
I had to comment the ipv4_address field
I should apologize for that
thanks @lunny

but I still have only small set of runner management via the instance
is any of this issue tasks already emplemented or applicable ?