actions / actions/checkout

actions/checkout@v2 fails on self-hosted RHEL 7 runner with "fatal: could not read Username for 'https://github.com': No such device or address"

Open
#397 2 comments 5 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
8.9k
Forks
2.8k
PR merge metrics
No merged PRs in 30d

Description

System Information

  • OS Version: RHEL 7.9 (Maipo)
  • Git Version: 2.29.2
  • Repo Access: Private

Steps to reproduce

  1. Install the Github Actions self-hosted runner service on a CentOS/RHEL 7 host.
  2. Create a simple workflow to checkout out the repo that initiated the run.
name: Checkout via Github Actions Test
on:
  push:
jobs:
  self-hosted-checkout-test:
    runs-on: self-hosted
    steps:
    # Force a clean up of any files left by a previous run.
    # Required since Actions will not do this for you.
    - name: Clean up files from the previous run
      run: rm -rf ./*

    - name: checkout repo to runner
      uses: actions/checkout@v2
  1. Run the workflow.

Result: Error: fatal: could not read Username for 'https://github.com': No such device or address

Troubleshooting steps taken

  • Provide a PAT from a user that has access to the repo using (example below). Same result.
    - name: checkout repo to runner
      uses: actions/checkout@v2
      with:
        token: ${{ secrets.GITHUB_PAT }}
  • Cloning the repo manually using a PAT in the workflow. This works.

Any advice on how to make this work or am I stuck using a traditional git clone in my workflow?

Contributor guide

Open the contributing guide

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.

Research direction

Start by reproducing the supplied checkout workflow on the stated RHEL 7.9 self-hosted runner, using both the default token and the PAT configuration. Compare this with the manual PAT-based clone that succeeds, then inspect the checkout action entry point and its authentication behavior. Done means identifying a reproducible cause and documenting a supported fix or confirmed limitation.

Written by the indexing model from the issue text.

Assessment

Tech stack
git, github-actions, typescript
Domain
ci-cd, devops
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.