hl128k Blog

一个bug改一天

0%

Docker 部署 Gitea Actions

发表于 更新于 分类于 ，

AI导读：本文记录了在本地部署Gitea并使用Gitea Actions的过程，主要讨论了部署过程中遇到的几个关键问题。首先，部署Gitea时使用了Docker-Compose，配置部分较为简单。重点是在部署act_runner时遇到的一些坑，特别是在配置和网络问题上。act_runner需要先生成配置文件，必须删除已有配置后才能生成新的config.yaml。其次，网络问题主要出现在GITEA_INSTANCE_URL参数上，因为Docker-Compose中的depends_on配置并未满足act_runner的网络需求，导致容器无法正确连接到Gitea。解决方案包括创建独立网络并配置固定IP，以确保网络连接正常。

前提

心血来潮想要使用自己的Actions,于是找了一遍现有的git服务器.
其中gitea 的 Gitea Actions可以基本无修改的兼容GitHub Actions,也就是说只要拉下来GitHub的项目就能在本地使用,不需要修改还是挺方便的
记录一下部署踩坑

部署

先放一下最终
Docker-Compose

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
version: '3.8'

services:
  gitea:
    image: gitea/gitea:latest
    container_name: gitea
    environment:
      - USER_UID=1000
      - USER_GID=1000
    volumes:
      - D:/gitea-data:/data  # 修改数据目录为 D:\gitea-data
    ports:
      - "3000:3000"
      - "222:22"
    restart: always

  runner:
    image: gitea/act_runner:latest
    container_name: act_runner
    depends_on:
      - gitea
    environment:
      - CONFIG_FILE=/config.yaml
      - GITEA_INSTANCE_URL=http://host.docker.internal:3000
      - GITEA_RUNNER_REGISTRATION_TOKEN=<TOKEN>  # 设置你的 Gitea Runner 注册令牌
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
      - D:/gitea-data/act_runner/config.yaml:/config.yaml
      - D:/gitea-data/act_runner/data:/data  # 设置 runner 的数据目录为 D:\gitea-data\act_runner
    restart: always

gitea部分没什么可说的基本配置
act_runner着重来说

  1. config生成

act_runner 需要先创建容器才能使用然后在容器内使用act_runner generate-config > config.yaml才能生成
所有要先删除CONFIG_FILE=/config.yaml和- D:/gitea-data/act_runner/config.yaml:/config.yaml生成一次才行
当然现在可以直接使用我的

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
# Example configuration file, it's safe to copy this as the default config file without any modification.

# You don't have to copy this file to your instance,
# just run `./act_runner generate-config > config.yaml` to generate a config file.

log:
  # 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" or "ubuntu-latest:docker://gitea/runner-images:ubuntu-latest"
  # Find more images provided by Gitea at https://gitea.com/gitea/runner-images .
  # If it's empty when registering, it will ask for inputting labels.
  # If it's empty when execute `daemon`, will use labels in `.runner` file.
  labels:
    - "ubuntu-latest:docker://gitea/runner-images:ubuntu-latest"
    - "ubuntu-22.04:docker://gitea/runner-images:ubuntu-22.04"
    - "ubuntu-20.04:docker://gitea/runner-images:ubuntu-20.04"

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: ""
  # The port of the cache server.
  # 0 means to use a random available port.
  port: 0
  # 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.
  # NOTE: There is no need to add the first '/' of the path as act_runner will add it automatically. 
  # If the path starts with '/', the '/' will be trimmed.
  # For example, if the parent directory is /path/to/my/dir, workdir_parent should be path/to/my/dir
  # 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: true
  # 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. 网络问题

这里的网络不是指连接GitHub和Docker Hub,是GITEA_INSTANCE_URL这个参数
因为使用的Docker-Compose习惯性的使用了depends_on,所以配置了GITEA_INSTANCE_URL:http://gitea:3000
但是这个并不是act_runner使用的,而且由act_runner生成的新的docker容器连接使用的,这个新的容器并不在Docker-Compose里面,所以http://gitea:3000是连不上的
所以这里要么像我一样使用宿主的地址或者使用外部网络
先执行
docker network create gitea-network
然后配置里增加

1
2
3
networks:
    gitea-network:
        external: true

networks里都增加固定ip,配置里填固定ip就可以了GITEA_INSTANCE_URL:http://<gitea IP>:3000,理论上是这样的,不过没有实践

欢迎关注我的其它发布渠道