Workflow jobs remain stuck in the “waiting” state indefinitely

Actions
1

I have a Gitea self-hosted runner set up on an internal network environment. My workflow jobs remain stuck in the “waiting” state indefinitely

config.yaml at act_runner container
labels
- ubuntu-22.04-slim:docker://{my private registry ip:port}/gitea/runner-images:ubuntu-22.04-slim
- ubuntu-20.04-slim:docker://{gitea/runner-images:ubuntu-20.04-slim


workflows .yaml file
runs-on: ubuntu-22.04-slim // stuck waiting status, and no log (log level=trace)
runs-on: ubuntu-20.04 // run failed, no such host, pulling from docker.io
2

same problem here. any advice?

3

Check to make sure the runner is active.
Check to make sure the gitea runner isn’t running some other job from a different project.
In my case my action was stuck because it was busy with another projects actions.

4

I have/ had the same issue, I also couldn’t cancel it, and sometimes restarting a failed job also didn’t work. I’ve noticed that there was disk pressure on my database (MariaDB) where my Gitea instance writes to.

After solving this problem my instance is way faster again and actions seems to be working more reliably