Resolving build failures on Linux Shell runners due to incorrect runner type
Platform Notice: Cloud Only - This article only applies to Atlassian products on the cloud platform.
Summary
When executing a build on a "Linux Shell" runner, the build fails with the following error messages during the build setup phase:
1
2
retry: Could not execute '6', giving up: No such file or directory
retry: 6 returned 1, backing off for 10 seconds and trying again...Diagnosis
The error messages indicate that the build process is attempting to execute a command (retry 6) that is failing in the current environment. This typically happens when a "Linux Docker" runner is used in an environment where a "Linux Shell" runner is expected.
Cause
The runner instance was created as a "Linux Docker" runner in the repository or workspace settings. When the build process expects a "Linux Shell" runner, it includes the retry 6 command, which may not be available in some Linux distributions, leading to the failure.
Solution
To resolve this issue, you need to delete the existing "Linux Docker" runner and recreate it as a "Linux Shell" runner
Was this helpful?