Pipelines Linux Shell Runner is unavailable
Platform Notice: Cloud Only - This article only applies to Atlassian products on the cloud platform.
Summary
Sometimes, when Running builds with Runners on Linux Shell set as platform, you may encounter the following error message:
1
Currently no online runner available that matches the required labels.Environment
Pipelines Runners, using the Linux Shell platform for its host.
Cause
This can have two possible root causes:
The host was not available at the time the build has been triggered.
The platform label was not properly set up on the bitbucket-pipelines.yml configuration file.
Solution
Please make sure that the host was online at the time the build was triggered. You can review your Runner.log (see this page to find this file) and confirm that the Runner was online at the time by checking the timestamps shown in the log.
If the host was indeed online at the time, please review your Runner.log file and confirm if the runs-on tags are set up as follows:
1
2
3
4
[...]
runs-on:
- self.hosted
- linux.shellRegarding the platform label, please ensure that you have added default labels in the pipeline YAML under the "runs-on" step.
Example:
1
2
3
4
[...]
runs-on:
- self.hosted
- windows"The default label is set to 'self.hosted,' and depending on the type of runners, additional default labels are assigned, such as 'linux' for Docker-based runners, 'linux.shell' for Linux shell-based runners, 'windows,' and 'macos.'
If the default labels are not defined, and only a custom label is specified in the pipeline YAML, as shown below:
1
2
3
[...]
runs-on:
- aws-ec2The runner agent will search for available runners with the custom label in combination with 'self.hosted' and 'linux' matching label runners. If they exist, the agent will proceed with the execution; otherwise, it will generate an error message: 'Currently, no online runner is available that matches the required labels'."
Was this helpful?