renovatebot / renovatebot/github-action

docker-cmd-file not working

Open
#817 8 comments 0 reactions 1 assignee View on GitHub

@lazytesting is already working on this.

Since Feb 9, 2024.

documentation enhancement
Dominant language
TypeScript
Stars
546
Forks
115
Avg merge
19h 4m
Merged PRs (30d)
10

Description

This issue is maybe related to https://github.com/renovatebot/github-action/issues/794 but that one does not contains a solution and I still got a stable reproduction scenario.

  1. In the action config file I set:
 with:
          docker-cmd-file: example/entrypoint.sh
  1. In the logs I see
/usr/bin/docker run --env LOG_LEVEL --env RENOVATE_TOKEN=*** --env RENOVATE_CONFIG_FILE=/github-action/renovate-config.js --volume /home/runner/work/test-renovate/test-renovate/example/renovate-config.js:/github-action/renovate-config.js --volume /home/runner/work/test-renovate/test-renovate/example/entrypoint.sh:/entrypoint.sh --user root --volume /tmp:/tmp --rm ghcr.io/renovatebot/renovate:37.175.3 /entrypoint.sh
...some unrelevant log lines...
DEBUG: CLI config "config": {"repositories": ["/entrypoint.sh"]}
  1. It seems that the /entrypoint.sh argument for docker run is not running the custom entrypoints script
  2. I think renovate gets called with this argument, like this:
renovate /entrypoint.sh

this would explain why it sees a cli config with this value als repositories at least.

I took the examples from this project and stripped it down to a minimal reproduction path.
code: https://github.com/lazytesting/test-renovate
action run: https://github.com/lazytesting/test-renovate/actions/runs/7829422258/job/21361374380

The strange thing is that it seems to work in the e2e test github action of this project but I cannot see the difference.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.