Github Action fails on fetching checkout v3 git bug The process '/usr/bin/git' failed with exit code 128

[yardensade]

Select Topic Area

Bug

Body

Many actions are all of a sudden failing today on checkout, absolutely nothing changed on my side.

This is the action step which I had for months:

runs:
  using: "composite"
  steps:
    - name: Check out ****-github-actions
      uses: actions/checkout@v3
      with:
        repository: ****-github-action
        ref: main
        path: ./.github/actions/****

Attaching logs:

2024-04-04T07:33:22.8383374Z ##[group]Run actions/checkout@v3
2024-04-04T07:33:22.8383775Z with:
2024-04-04T07:33:22.8384133Z   repository: ****
2024-04-04T07:33:22.8384632Z   ref: main
2024-04-04T07:33:22.8384970Z   path: ./.github/actions/****
2024-04-04T07:33:22.8385641Z   token: ****
2024-04-04T07:33:22.8385991Z   ssh-strict: true
2024-04-04T07:33:22.8386320Z   persist-credentials: true
2024-04-04T07:33:22.8386662Z   clean: true
2024-04-04T07:33:22.8386998Z   sparse-checkout-cone-mode: true
2024-04-04T07:33:22.8387342Z   fetch-depth: 1
2024-04-04T07:33:22.8387633Z   fetch-tags: false
2024-04-04T07:33:22.8388019Z   lfs: false
2024-04-04T07:33:22.8388302Z   submodules: false
2024-04-04T07:33:22.8388649Z   set-safe-directory: true
2024-04-04T07:33:22.8388989Z ##[endgroup]
2024-04-04T07:33:23.0326554Z Syncing repository: ****
2024-04-04T07:33:23.0328818Z ##[group]Getting Git version info
2024-04-04T07:33:23.0330105Z Working directory is '/home/runner/work/****'
2024-04-04T07:33:23.0331231Z [command]/usr/bin/git version
2024-04-04T07:33:23.0367581Z git version 2.43.2
2024-04-04T07:33:23.0392396Z ##[endgroup]
2024-04-04T07:33:23.0414859Z Temporarily overriding HOME='/home/runner/work/_temp/d405e998-3c6c-4296-9916-fbb53712203f' before making global git config changes
2024-04-04T07:33:23.0417435Z Adding repository directory to the temporary git global config as a safe directory
2024-04-04T07:33:23.0420012Z [command]/usr/bin/git config --global --add safe.directory /home/runner/work****
2024-04-04T07:33:23.0457392Z ##[group]Initializing the repository
2024-04-04T07:33:23.0479936Z [command]/usr/bin/git init /home/runner/work/****
2024-04-04T07:33:23.0542829Z hint: Using 'master' as the name for the initial branch. This default branch name
2024-04-04T07:33:23.0545017Z hint: is subject to change. To configure the initial branch name to use in all
2024-04-04T07:33:23.0546604Z hint: of your new repositories, which will suppress this warning, call:
2024-04-04T07:33:23.0547984Z hint: 
2024-04-04T07:33:23.0549297Z hint: 	git config --global init.defaultBranch <name>
2024-04-04T07:33:23.0550537Z hint: 
2024-04-04T07:33:23.0552992Z hint: Names commonly chosen instead of 'master' are 'main', 'trunk' and
2024-04-04T07:33:23.0555023Z hint: 'development'. The just-created branch can be renamed via this command:
2024-04-04T07:33:23.0556710Z hint: 
2024-04-04T07:33:23.0557845Z hint: 	git branch -m <name>
2024-04-04T07:33:23.0559837Z Initialized empty Git repository in /home/runner/work/****
2024-04-04T07:33:23.0564373Z [command]/usr/bin/git remote add origin https://github.com/****
2024-04-04T07:33:23.0599952Z ##[endgroup]
2024-04-04T07:33:23.0601276Z ##[group]Disabling automatic garbage collection
2024-04-04T07:33:23.0603564Z [command]/usr/bin/git config --local gc.auto 0
2024-04-04T07:33:23.0632098Z ##[endgroup]
2024-04-04T07:33:23.0633569Z ##[group]Setting up auth
2024-04-04T07:33:23.0639491Z [command]/usr/bin/git config --local --name-only --get-regexp core\.sshCommand
2024-04-04T07:33:23.0667251Z [command]/usr/bin/git submodule foreach --recursive sh -c "git config --local --name-only --get-regexp 'core\.sshCommand' && git config --local --unset-all 'core.sshCommand' || :"
2024-04-04T07:33:23.0965730Z [command]/usr/bin/git config --local --name-only --get-regexp http\.https\:\/\/github\.com\/\.extraheader
2024-04-04T07:33:23.0978576Z [command]/usr/bin/git submodule foreach --recursive sh -c "git config --local --name-only --get-regexp 'http\.https\:\/\/github\.com\/\.extraheader' && git config --local --unset-all 'http.https://github.com/.extraheader' || :"
2024-04-04T07:33:23.1155656Z [command]/usr/bin/git config --local http.https://github.com/.extraheader AUTHORIZATION: basic ***
2024-04-04T07:33:23.1195621Z ##[endgroup]
2024-04-04T07:33:23.1197545Z ##[group]Fetching the repository
2024-04-04T07:33:23.1206635Z [command]/usr/bin/git -c protocol.version=2 fetch --no-tags --prune --progress --no-recurse-submodules --depth=1 origin +refs/heads/main*:refs/remotes/origin/main* +refs/tags/main*:refs/tags/main*
2024-04-04T07:33:23.1258870Z /usr/lib/git-core/git-remote-https: error while loading shared libraries: /lib/x86_64-linux-gnu/libgssapi_krb5.so.2: invalid ELF header
2024-04-04T07:33:23.1266961Z The process '/usr/bin/git' failed with exit code 128
2024-04-04T07:33:23.1268196Z Waiting 16 seconds before trying again
2024-04-04T07:33:39.1303048Z [command]/usr/bin/git -c protocol.version=2 fetch --no-tags --prune --progress --no-recurse-submodules --depth=1 origin +refs/heads/main*:refs/remotes/origin/main* +refs/tags/main*:refs/tags/main*
2024-04-04T07:33:39.1341658Z /usr/lib/git-core/git-remote-https: error while loading shared libraries: /lib/x86_64-linux-gnu/libgssapi_krb5.so.2: invalid ELF header
2024-04-04T07:33:39.1352537Z The process '/usr/bin/git' failed with exit code 128
2024-04-04T07:33:39.1353281Z Waiting 19 seconds before trying again
2024-04-04T07:33:58.1456060Z [command]/usr/bin/git -c protocol.version=2 fetch --no-tags --prune --progress --no-recurse-submodules --depth=1 origin +refs/heads/main*:refs/remotes/origin/main* +refs/tags/main*:refs/tags/main*
2024-04-04T07:33:58.1494241Z /usr/lib/git-core/git-remote-https: error while loading shared libraries: /lib/x86_64-linux-gnu/libgssapi_krb5.so.2: invalid ELF header
2024-04-04T07:33:58.1571200Z ##[error]The process '/usr/bin/git' failed with exit code 128

[Moshikol]

This exact issue happens to me as well, any fixes?

[cfrepak]

same error here too. yesterday, same repo, same code was working fine.

[yardensade]

I opened issue in: actions/runner-images#9632
But they ran it twice and seem to ignore this as working, even tho I explained to them this happens sporadically.