背景

入门gitea中，我们第一次发现gitea actions运行截图：仓库导航 -> Acitons -> 左侧导航所有工作流 -> 点击查看详情

这里的没有runner在线，是因为我们只部署了gitea，没有配置gitea action，可以部署一个Act-Runner

Gitea Actions是源于Github Actions的一个项目，是基于Github Actions开源项目改造而来，同时也兼容了Github Actions绝大多数的功能。大多数情况下可以无缝切换的使用。

官方教程：https://docs.gitea.com/usage/actions/act-runner

安装

这里同样是使用Docker Compose进行安装，安装之前先在部署好的Gitea上去获取Token用于注册Runner。

1. 先登录管理员账户。通过头像下拉菜单、管理后台、Actions、Runners的路径可以找到系统级的Runners列表，在这里注册的Runners可以被任何仓库、组织使用。
2. 点击创建Runner，复制显示的Token。
3. 修改Compose文件， 运行即可。

在运行前需要先生成一下配置文件:

cd /var/lib/docker/volumes/act_runner/_data
docker run --entrypoint="" --rm -it gitea/act_runner:latest act_runner generate-config > config.yaml

这里我复制了一份出来：

需要配置一下 cache.host，用于保存缓存用的，端口也需要映射出来

config.yaml：

# The level of logging, can be trace, debug, info, warn, error, fatal
level: info

runner:
  # Where to store the registration result.
  file: .runner
  # Execute how many tasks concurrently at the same time.
  capacity: 1
  # Extra environment variables to run jobs.
  envs:
    A_TEST_ENV_NAME_1: a_test_env_value_1
    A_TEST_ENV_NAME_2: a_test_env_value_2
  # Extra environment variables to run jobs from a file.
  # It will be ignored if it's empty or the file doesn't exist.
  env_file: .env
  # The timeout for a job to be finished.
  # Please note that the Gitea instance also has a timeout (3h by default) for the job.
  # So the job could be stopped by the Gitea instance if it's timeout is shorter than this.
  timeout: 3h
  # Whether skip verifying the TLS certificate of the Gitea instance.
  insecure: false
  # The timeout for fetching the job from the Gitea instance.
  fetch_timeout: 5s
  # The interval for fetching the job from the Gitea instance.
  fetch_interval: 2s
  # The labels of a runner are used to determine which jobs the runner can run, and how to run them.
  # Like: ["macos-arm64:host", "ubuntu-latest:docker://node:16-bullseye", "ubuntu-22.04:docker://node:16-bullseye"]
  # If it's empty when registering, it will ask for inputting labels.
  # If it's empty when execute `deamon`, will use labels in `.runner` file.
  labels: []

cache:
  # Enable cache server to use actions/cache.
  enabled: true
  # The directory to store the cache data.
  # If it's empty, the cache data will be stored in $HOME/.cache/actcache.
  dir: ""
  # The host of the cache server.
  # It's not for the address to listen, but the address to connect from job containers.
  # So 0.0.0.0 is a bad choice, leave it empty to detect automatically.
  host: "填入宿主机IP"
  # The port of the cache server.
  # 0 means to use a random available port.
  port: 9010
  # The external cache server URL. Valid only when enable is true.
  # If it's specified, act_runner will use this URL as the ACTIONS_CACHE_URL rather than start a server by itself.
  # The URL should generally end with "/".
  external_server: ""

container:
  # Specifies the network to which the container will connect.
  # Could be host, bridge or the name of a custom network.
  # If it's empty, act_runner will create a network automatically.
  network: ""
  # Whether to use privileged mode or not when launching task containers (privileged mode is required for Docker-in-Docker).
  privileged: false
  # And other options to be used when the container is started (eg, --add-host=my.gitea.url:host-gateway).
  options:
  # The parent directory of a job's working directory.
  # If it's empty, /workspace will be used.
  workdir_parent:
  # Volumes (including bind mounts) can be mounted to containers. Glob syntax is supported, see https://github.com/gobwas/glob
  # You can specify multiple volumes. If the sequence is empty, no volumes can be mounted.
  # For example, if you only allow containers to mount the `data` volume and all the json files in `/src`, you should change the config to:
  # valid_volumes:
  #   - data
  #   - /src/*.json
  # If you want to allow any volume, please use the following configuration:
  # valid_volumes:
  #   - '**'
  valid_volumes: []
  # overrides the docker client host with the specified one.
  # If it's empty, act_runner will find an available docker host automatically.
  # If it's "-", act_runner will find an available docker host automatically, but the docker host won't be mounted to the job containers and service containers.
  # If it's not empty or "-", the specified docker host will be used. An error will be returned if it doesn't work.
  docker_host: ""
  # Pull docker image(s) even if already present
  force_pull: false
  # Rebuild docker image(s) even if already present
  force_rebuild: false

host:
  # The parent directory of a job's working directory.
  # If it's empty, $HOME/.cache/act/ will be used.
  workdir_parent:

1. 创建用于持久化存储 act_runner 数据的目录（命名规则参考）
   /mnt/sda1-16t/data/act_runner

创建存储卷，nfs映射到pve目录。

同时目录下保存一份上述config.yaml

2. 点击 portainer 控制面板左侧 Stacks（堆栈） ，在该页面中点击 Add stack（新建）

为 Stack 命名，根据需要修改下面提供的模板并粘贴到页面上，然后点击页面底部 Deploy the stack 完成创建

version: "3.8"
services:
  runner:
    image: gitea/act_runner:latest
    restart: always
    privileged: true
    environment:
      CONFIG_FILE: ./config.yaml
      GITEA_INSTANCE_URL: "http://x.x.x.x:3000"   # gitea访问地址
      GITEA_RUNNER_REGISTRATION_TOKEN: ""   # 前面获得的token
      GITEA_RUNNER_NAME: "docker101"                     # 自定义Runner的名称用于显示
      GITEA_RUNNER_LABELS: "ubuntu-latest"               # 暂时不建议修改
      DOCKER_HOST: unix:///var/run/docker.sock           # 这是docker的套接字，用于Docker in Docker
    ports:
      - 9010:9010 # 这里是映射缓存端口
    volumes:
      - /var/lib/docker/volumes/act_runner/_data/config.yaml:/config.yaml # 配置文件
      - /var/lib/docker/volumes/act_runner/_data:/data           # 数据文件
      - /var/run/docker.sock:/var/run/docker.sock
    networks:
      photoprism-net:                  #共用的网络,gitea在

networks:
 photoprism-net:                      #共用的网络,gitea在
   external: true

启动后，在Gitea的Runners列表中就可以看到刚刚注册进行的Runner了。