runner: Error: Can't use 'tar -xzf' extract archive file
Describe the bug
Can’t use runner. getting below error while running actions
Getting action download info Download action repository ‘actions/checkout@v2’ (SHA:7884fcad6b5d53d10323aee724dc68d8b9096a2e) Download action repository ‘actions/setup-python@v2’ (SHA:7f80679172b057fc5e90d70d197929d454754a5a) Error: Can’t use ‘tar -xzf’ extract archive file: /home/runner/work/_actions/_temp_fcaba673-8301-4f09-b4c0-658716c016e9/0f75c0dd-581a-4910-aa5c-6a5cc9a53620.tar.gz. return code: 2.
To Reproduce Steps to reproduce the behavior:
- run github actions
Expected behavior
actions should be complete without any errors
Runner Version and Platform
Current runner version: ‘2.291.1’
OS of the machine running the runner? OSX/Windows/Linux/…
What’s not working?
Current runner version: '2.291.1'
Operating System
Virtual Environment
Virtual Environment Provisioner
GITHUB_TOKEN Permissions
Secret source: None
Prepare workflow directory
Prepare all required actions
Getting action download info
Download action repository 'actions/checkout@v2' (SHA:7884fcad6b5d53d10323aee724dc68d8b9096a2e)
Download action repository 'actions/setup-python@v2' (SHA:7f80679172b057fc5e90d70d197929d454754a5a)
Error: Can't use 'tar -xzf' extract archive file: /home/runner/work/_actions/_temp_fcaba673-8301-4f09-b4c0-658716c016e9/0f75c0dd-581a-4910-aa5c-6a5cc9a53620.tar.gz. return code: 2.
Job Log Output
If applicable, include the relevant part of the job / step log output here. All sensitive information should already be masked out, but please double-check before pasting here.
Runner and Worker’s Diagnostic Logs
If applicable, add relevant diagnostic log information. Logs are located in the runner’s _diag
folder. The runner logs are prefixed with Runner_
and the worker logs are prefixed with Worker_
. Each job run correlates to a worker log. All sensitive information should already be masked out, but please double-check before pasting here.
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Reactions: 126
- Comments: 65 (4 by maintainers)
Commits related to this issue
- Bump actions/checkout from v3 to v3.1.0 (#5335) See https://github.com/actions/runner/issues/1923 and https://github.com/actions/checkout/issues/948 — committed to projectnessie/nessie by snazy 2 years ago
- fix: checkout@v3 -> checkout@v4 Error: Can't use 'tar -xzf' extract archive file https://github.com/actions/runner/issues/1923 — committed to smeghead/php-class-diagram by smeghead 10 months ago
This particular issue seems to be back
We can see the issue started appearing again.
I confirm that there are multiple users experiencing this issue again https://github.com/orgs/community/discussions/26321#discussioncomment-3813182
All workflows are broken and not running, github should treat this as a major incident and update their status page: https://www.githubstatus.com/
we are looking at this now…
We are currently experiencing this
Yes, I agree with @j-nix : the same error come back on my workflow today.
It seems that this issue has been fixed now. My latest job ran past the failure it halted at earlier.
FAILED
🔴PASSED
🟢actions/setup-node@v3
was not downloaded properly due to a server side bug. We applied a server side fix and this should be good now base on our telemetry. Sorry for the inconvenice. 🙇The incident has been resolved. Thank you.
@levrik I had the same issue with actions/cache , it might not be something specific to that action
yup its back
And it’s back…
Again for us. Nothing is working.
@TingluoHuang Still happening: https://github.com/upptime/upptime/actions/runs/2747365664
Seems like there is an issue with downloads from GitHub now causing this. Not necessarily related to this runner, but no relevant issues show up on the status page yet
Tracked on https://www.githubstatus.com/incidents/76xp2jd3px64 now.
@thboop We experience this issue since a few minutes 😕
Maybe jumping from v2 to v3 invalidates the cache, and then you’re essentially just working around the problem?
Hey folks,
A server side bug caused this issue, we’ve since mitigated the problem, please let us know if you see it again.
Thank you for your patience while we addressed it and sorry for the trouble it may have caused you
fails for me on about 30% of matrix jobs
I’ve been seeing on and off starting today.
Didn’t even make it to the first line of code 😄
Same error. Just when I need workflows, everything hinders me.
Our workflow is running again - maybe someone cleaned up the cache?
I can confirm that
GitHub Actions 2
seems to always fail. Succeeding runs were onGitHub Actions 5
for me.Well, here we go again.
@fabiofdsantos we clean up the bad cache, things should be back to normal.
@thboop Just got this error as well - 5 times in a row. The log looks like this:
My failing and succeeding run differ in that the failing run ran on
Github Actions 2 (hosted)
while the succeeding one ran onHosted Agent (hosted)
Successful run:
@claudesky Then just coincidence that that first log I saw here was failing on the exact same action. Still weird that the workflows using the Cypress action are the only ones failing for us… at least so far.