You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am running a Forgejo runner (which uses act under the hood) in conjunction with Podman. In general this works fine, but there's an issue with creating network names if the job-id's have spaces in them. The issue appears to occur here. Specifically, Podman requires network names to conform to the regex [a-zA-Z0-9][a-zA-Z0-9_.-]*, but obviously, if the job-id contains one or more spaces, this will not be the case.
I've already submitted a bug report for Forgejo Runner, and that contains more information on how exactly I am running it.
I'm sorry for this slightly unconventional bug report, but I couldn't really fit it in the common bug template, as I'm not running act directly.
I would turn this issue more towards, missing job-id validation of forgejo.
Please verify that issues you open here can be reproduced on our side.
jobs like this are early failed
on: pushjobs:
hello world:
runs-on: ubuntu-lateststeps:
- name: Hello worldrun: echo Hello world
INFO[0000] Using docker host 'unix:///var/run/docker.sock', and daemon socket 'unix:///var/run/docker.sock'
Error: workflow is not valid. 'x.yml': Job name 'hello world' is invalid. Names must start with a letter or '_' and contain only alphanumeric characters, '-', or '_'
I am running a Forgejo runner (which uses act under the hood) in conjunction with Podman. In general this works fine, but there's an issue with creating network names if the
job-id
's have spaces in them. The issue appears to occur here. Specifically, Podman requires network names to conform to the regex[a-zA-Z0-9][a-zA-Z0-9_.-]*
, but obviously, if thejob-id
contains one or more spaces, this will not be the case.I've already submitted a bug report for Forgejo Runner, and that contains more information on how exactly I am running it.
I'm sorry for this slightly unconventional bug report, but I couldn't really fit it in the common bug template, as I'm not running act directly.
Software versions
I am running:
code.forgejo.org/forgejo/runner:6.2.2
Podman
Workflow Content
Relevant Log Output
The text was updated successfully, but these errors were encountered: