fix(renovate): run renovate image directly instead of docker-wrapping action
All checks were successful
CI / ci (push) Successful in 1m52s

renovatebot/github-action is a Node wrapper that shells out to
`docker run ghcr.io/renovatebot/renovate`, requiring a Docker CLI + socket
inside the job. The Gitea runner executes the job in a plain node:22 container
with neither, so it died on "Unable to locate executable file: docker".

Run the renovate image as the job container and invoke `renovate` directly —
drops the docker-in-docker requirement. Full tag pinned; Renovate's
github-actions manager keeps container.image bumped.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
2026-06-19 10:08:08 +02:00
parent eeef089e4a
commit 35022267dc

View File

@@ -16,11 +16,18 @@ concurrency:
jobs: jobs:
renovate: renovate:
runs-on: docker runs-on: docker
# Run the Renovate image *as* the job container and invoke the `renovate`
# binary directly. The renovatebot/github-action wrapper is a thin Node
# action that shells out to `docker run …` — it needs a Docker CLI + socket
# inside the job, which the Gitea runner's plain node container has not, so
# it died on "Unable to locate executable file: docker". Running the image
# directly drops the docker-in-docker requirement entirely.
# Full tag pinned; Renovate's github-actions manager keeps it bumped.
container:
image: ghcr.io/renovatebot/renovate:43.232.0
steps: steps:
- name: Run Renovate - name: Run Renovate
# This action publishes only full semver tags (no moving major tag — run: renovate
# @v46 / @v40 etc. 404). Pin a real release; Renovate keeps it bumped.
uses: renovatebot/github-action@v46.1.15
env: env:
# Self-hosted Gitea, not github.com. # Self-hosted Gitea, not github.com.
RENOVATE_PLATFORM: gitea RENOVATE_PLATFORM: gitea