Supporting material for my blog post: https://mteixeira.wordpress.com/2025/02/16/running-renovate-on-self-hosted-forgejo/

forgejo-runner-workflow-renovate.yaml

name: Renovate

on:
  schedule:
    # The "*" (#42, asterisk) character has special semantics in YAML, so this
    # string has to be quoted.
    - cron: '0/15 * * * *'

jobs:
  renovate:
    runs-on: catthehacker-arm64
    steps:
      - name: Checkout
        uses: actions/checkout@v4

      - name: Run self-hosted Renovate
        uses: https://github.com/renovatebot/github-action@v41.0.13
        with:
          docker-network: host
          env-regex: "^(?:RENOVATE_\\w+|LOG_LEVEL|NODE_EXTRA_CA_CERTS)$"
          docker-volumes: |
            /etc/ssl/certs/ca-certificates.crt:/etc/ssl/certs/ca-certificates.crt:ro ;
            /usr/local/share/ca-certificates/homelab-ca.crt:/usr/local/share/ca-certificates/homelab-ca.crt:ro
        env:
          # LOG_LEVEL: "debug"
          DOCKER_HOST: ${{ env.DOCKER_HOST }}
          RENOVATE_ENDPOINT: ${{ github.api_url }}
          RENOVATE_PLATFORM: "gitea"
          RENOVATE_TOKEN: ${{ secrets.RENOVATE_TOKEN }}
          RENOVATE_REPOSITORIES: ${{ github.repository }}
          RENOVATE_GITHUB_COM_TOKEN: ${{ secrets.RENOVATE_GITHUB_COM_TOKEN }}
          NODE_EXTRA_CA_CERTS: "/usr/local/share/ca-certificates/homelab-ca.crt"

@badnetmask: I love your Forgejo guides! I'm currently stuck on linking Renovate with Forgejo Actions. When running my yaml via Forgejo Actions, I get an error stating that Forgejo is unable to find 'docker'.

My workaround was to run a separate Renovate Docker container with all of the RENOVATE_ values. It works, but it's not a smooth experience.

Can you share your Docker compose files for Renovate with your secrets redacted for comparison. I can share mine as well if that's helpful.