Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

gitconfig not found #147

Open
mxw-sec opened this issue Jan 8, 2025 · 3 comments
Open

gitconfig not found #147

mxw-sec opened this issue Jan 8, 2025 · 3 comments
Labels
bug Something isn't working

Comments

@mxw-sec
Copy link

mxw-sec commented Jan 8, 2025

Describe the bug

Using Self Hosted Runners, on Kubernetes I am not able to get the action to finalize. It continues to state [/github/home/.git](error: could not lock config file /github/home/.gitconfig: No such file or directory)

How can we reproduce it?

This is my file that I am using with a self-hosted-runner-set
name: Generate terraform docs
on:
workflow_dispatch:

jobs:
docs:
runs-on: arc-runner-set
container:
image: alpine:latest

steps:
  - uses: actions/checkout@v4
    #with:
    #ref: ${{ github.event.pull_request.head.ref }}


  - name: Render terraform docs inside the README.md and push changes back to PR branch
    uses: terraform-docs/[email protected]
    with:
      working-dir: ./resources/root/src,./resources/workloads/core_app/src,./resources/workloads/keywords/src,
      output-file: readme.md
      output-method: inject
      git-push: "true"

Environment information

I know this works on Github Hosted runners, but its not working on a self hosted runner. and I have tried a lot of different operating systems for the container.

I have even tried manually creating the file.

@mxw-sec mxw-sec added the bug Something isn't working label Jan 8, 2025
@khos2ow
Copy link
Member

khos2ow commented Jan 9, 2025

This very much sounds like the long standing actions/runner#863 issue. Specially for the fact that you mentioned it works properly in hosted runners.

I suggest try one of the recommended workarounds (like this) and see if it helps, or the issue is really from this action.

@mxw-sec
Copy link
Author

mxw-sec commented Jan 9, 2025

Its also Mentioned Here, and alot of packages have had to change the git commit scopes to --system instead of global.

@mxw-sec
Copy link
Author

mxw-sec commented Jan 9, 2025

update

The Mentioned Workaround doesn't appear to fix it @khos2ow

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants