Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

service docker exceeded memory limit

Suthakar Ganeshamoorthy
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
August 3, 2023

Service docker exceed the memory limit, how to fix the following issue ?


Docker Failed.png





1 answer

0 votes
Theodora Boudale
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
August 7, 2023

Hi @Suthakar Ganeshamoorthy,

Regular build steps have 4096 MB of memory in total, while large build steps (which you can define using size: 2x) have 8192 MB in total. Service containers get 1024 MB memory by default if you haven't specified a different memory limit in your bitbucket-pipelines.yml file.

The error means that your Docker service does not have enough memory. You can increase the memory of the service in your bitbucket-pipelines.yml file.

If the service is used in a regular step, its memory can be increased up to 3072 MB. If the service is used in a large step (with the size: 2x option), its memory can be increased up to 7128 MB.

You can check the following documentation for more information and also an example of how to configure memory for a service:

All the above applies to builds that run in Atlassian infrastructure. If you are using a self-hosted Linux Docker Runner you can configure 4x and 8x steps (if the host machine has that memory), which means you can increase the service memory up to 15360 MB and 31744 MB respectively.

Please feel free to let me know if you have any questions.

Kind regards,

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events