71 lines
5.4 KiB
YAML
71 lines
5.4 KiB
YAML
apiVersion: v1
|
|
data:
|
|
config.yaml: "# Example configuration file, it's safe to copy this as the default
|
|
config file without any modification.\n\n# You don't have to copy this file to
|
|
your instance,\n# just run `./act_runner generate-config > config.yaml` to generate
|
|
a config file.\n\nlog:\n # The level of logging, can be trace, debug, info, warn,
|
|
error, fatal\n level: info\n\nrunner:\n # Where to store the registration result.\n
|
|
\ file: .runner\n # Execute how many tasks concurrently at the same time.\n capacity:
|
|
1\n # Extra environment variables to run jobs.\n envs:\n A_TEST_ENV_NAME_1:
|
|
a_test_env_value_1\n A_TEST_ENV_NAME_2: a_test_env_value_2\n # Extra environment
|
|
variables to run jobs from a file.\n # It will be ignored if it's empty or the
|
|
file doesn't exist.\n env_file: .env\n # The timeout for a job to be finished.\n
|
|
\ # Please note that the Gitea instance also has a timeout (3h by default) for
|
|
the job.\n # So the job could be stopped by the Gitea instance if it's timeout
|
|
is shorter than this.\n timeout: 3h\n # The timeout for the runner to wait for
|
|
running jobs to finish when shutting down.\n # Any running jobs that haven't
|
|
finished after this timeout will be cancelled.\n shutdown_timeout: 0s\n # Whether
|
|
skip verifying the TLS certificate of the Gitea instance.\n insecure: false\n
|
|
\ # The timeout for fetching the job from the Gitea instance.\n fetch_timeout:
|
|
5s\n # The interval for fetching the job from the Gitea instance.\n fetch_interval:
|
|
2s\n # The labels of a runner are used to determine which jobs the runner can
|
|
run, and how to run them.\n # Like: \"macos-arm64:host\" or \"ubuntu-latest:docker://gitea/runner-images:ubuntu-latest\"\n
|
|
\ # Find more images provided by Gitea at https://gitea.com/gitea/runner-images
|
|
.\n # If it's empty when registering, it will ask for inputting labels.\n #
|
|
If it's empty when execute `daemon`, will use labels in `.runner` file.\n labels:\n
|
|
\ - \"ubuntu-latest:docker://gitea/runner-images:ubuntu-latest\"\n - \"ubuntu-latest:docker://debian:stable-slim\"\n
|
|
\ - \"host-runner:host\"\n - \"ubuntu-22.04:docker://gitea/runner-images:ubuntu-22.04\"\n
|
|
\ - \"ubuntu-20.04:docker://gitea/runner-images:ubuntu-20.04\"\n\ncache:\n #
|
|
Enable cache server to use actions/cache.\n enabled: true\n # The directory
|
|
to store the cache data.\n # If it's empty, the cache data will be stored in
|
|
$HOME/.cache/actcache.\n dir: \"\"\n # The host of the cache server.\n # It's
|
|
not for the address to listen, but the address to connect from job containers.\n
|
|
\ # So 0.0.0.0 is a bad choice, leave it empty to detect automatically.\n host:
|
|
\"\"\n # The port of the cache server.\n # 0 means to use a random available
|
|
port.\n port: 0\n # The external cache server URL. Valid only when enable is
|
|
true.\n # If it's specified, act_runner will use this URL as the ACTIONS_CACHE_URL
|
|
rather than start a server by itself.\n # The URL should generally end with \"/\".\n
|
|
\ external_server: \"\"\n\ncontainer:\n # Specifies the network to which the
|
|
container will connect.\n # Could be host, bridge or the name of a custom network.\n
|
|
\ # If it's empty, act_runner will create a network automatically.\n network:
|
|
\"\"\n # Whether to use privileged mode or not when launching task containers
|
|
(privileged mode is required for Docker-in-Docker).\n privileged: false\n #
|
|
And other options to be used when the container is started (eg, --add-host=my.gitea.url:host-gateway).\n
|
|
\ options: '--volume /mnt/runner-cache:/toolcache'\n # The parent directory of
|
|
a job's working directory.\n # NOTE: There is no need to add the first '/' of
|
|
the path as act_runner will add it automatically. \n # If the path starts with
|
|
'/', the '/' will be trimmed.\n # For example, if the parent directory is /path/to/my/dir,
|
|
workdir_parent should be path/to/my/dir\n # If it's empty, /workspace will be
|
|
used.\n workdir_parent:\n # Volumes (including bind mounts) can be mounted to
|
|
containers. Glob syntax is supported, see https://github.com/gobwas/glob\n #
|
|
You can specify multiple volumes. If the sequence is empty, no volumes can be
|
|
mounted.\n # 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:\n valid_volumes:\n
|
|
\ - '/mnt/runner-cache/**'\n # - data\n # - /src/*.json\n # If you want
|
|
to allow any volume, please use the following configuration:\n # valid_volumes:\n
|
|
\ # - '**'\n# valid_volumes: []\n # overrides the docker client host with
|
|
the specified one.\n # If it's empty, act_runner will find an available docker
|
|
host automatically.\n # 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.\n # If it's not empty or \"-\", the specified docker
|
|
host will be used. An error will be returned if it doesn't work.\n docker_host:
|
|
\"\"\n # Pull docker image(s) even if already present\n force_pull: false\n
|
|
\ # Rebuild docker image(s) even if already present\n force_rebuild: false\n\nhost:\n
|
|
\ # The parent directory of a job's working directory.\n # If it's empty, $HOME/.cache/act/
|
|
will be used.\n workdir_parent:\n"
|
|
kind: ConfigMap
|
|
metadata:
|
|
creationTimestamp: null
|
|
name: gitea-runner-configfile
|
|
namespace: gitea
|