memory issue: while running bitbucket self hosted pipeline runner

Question

Hi Team,

While running a self-hosted runner I am getting the below error, even though I have memory space in my system and disabled swap.

before it was working fine, but suddenly stopped working since from 3 days,

Status: Downloaded newer image for docker-public.packages.atlassian.com/sox/atlassian/bitbucket-pipelines-runner:1
+ ./entrypoint.sh
[0.005s][warning][os,thread] Failed to start thread "GC Thread#0" - pthread_create failed (EPERM) for attributes: stacksize: 1024k, guardsize: 4k, detached.
#
# There is insufficient memory for the Java Runtime Environment to continue.
# Cannot create worker GC thread. Out-of-system resources.
# An error report file with more information is saved as:
# /opt/atlassian/pipelines/runner/hs_err_pid10.log

system resources:

1) ubuntu 20.04 LTS

2) 8gb RAM machine

Please help on this !!

Patrik S · Accepted Answer

Hello @ajaygodugu ,

Welcome to Atlassian Community!

From the error you reported, it seems you are using Linux Docker runners and the runner container is failing to start due to memory issues.

In this case, I would like to check the following with you :

* Could you confirm you are executing the runner in a Supported platform, that also meets the minimum requirements for Linux Docker runners ? Please also share the output of cat /etc/os-release

* Can you update the runner image in your local docker to the latest version using the command belowdocker image pull docker-public.packages.atlassian.com/sox/atlassian/bitbucket-pipelines-runner:1

and then try to Start a new runner ? 
* Could you download and update your Docker to the latest version from the Official Docker website

If after following those steps you are still facing issues when starting the Linux docker runner, if possible, please try testing starting the runner in a different machine to see if the same error is reproducible.

Let me know in case you have any questions.

Thank you, @ajaygodugu .

Patrik S

ajaygodugu · Accepted Answer

Thank you @Patrik S ,

The issue is resolved now, tested it in a new machine ( 20.04 LTS Ubuntu and 4GB RAM) before I was trying the machine had the same config but The one, which I upgraded from 18.04 LTS to 20.04 LTS (focal), not sure why it has failed due to memory issue, now it's working as expected (20.04 LTS with 4 GB Ram, without any 1x, or 2x-Steps.

thanks a lot for the support again !!