Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Error: Can't use 'tar -xzf' extract archive file

See original GitHub issue

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.