Is there a platform documentation?

[datenimperator]

First, many thx for act! Very valuable.

I'm looking into running jobs on my own image, via the runs-on param. I understood that a runner needs to be configured to provide a platform, and a job will be distributed to a runner only if the platform requirement matches the configuration.

With that in mind, I'm curious about the platform definition. In the runners config.yaml we have:

runner:
  # 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"

I have some questions here, which can't be answered from the given link.

• Which syntax is supported here? host, docker... else?
• Can I use wildcards, eg for versions?
• How does host work in particular? Security, filesystem...
• Are there any basic requirements for a custom image, to work with act?

Much appreciated if anybody could share some insights. Regards

Christian

[panekj]

You should ask in Gitea project, if you are using Gitea Runner

[ChristopherHX]

• How does host work in particular? Security, filesystem...

Just like a GitHub Runner works, there's no security. Expect your entire system to be compromised.

The only escape is a --ephemeral runner option or trusting everyone running jobs on your runner, to preserve your Gitea User Data from damage. (Same for GitHub Actions). And terminating/purging the runner Instance

• Are there any basic requirements for a custom image, to work with act?

For composite and docker actions, no requirements for images.

For nodejs actions, which most actions are you need node installed in PATH of your container. PATH is the env Variable in image metadata, not in some files.