You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Hi @Vikram Kumar,
In Pipelines builds, regular steps have 4096 MB of memory in total. The build container is given 1024 MB of the total memory.
Pipes use a Docker service, which has a default memory limit of 1024 MB. If the pipe needs more memory than that, I would suggest increasing that limit, you can do that in the definitions section of your bitbucket-pipelines.yml file. E.g. if you want to increase the memory of the Docker service to 2048 MB, you can use a definition as follows:
This will allocate 2048 MB of memory to the Docker service. You can also try increasing it to more, if this is not enough, up to 3072 MB (since the build container is given 1024 MB of the total memory).
If the Docker service needs more than 3072 MB, then you can increase the total memory available to a step by using size: 2x for a step. This will give the step 8 GB of memory, and then the Docker service can be configured to use up to 7128 MB.
Please keep in mind that pipelines configured with 2x will use twice the number of build minutes.
If you have any questions, please feel free to let me know.