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
How to fix the `Container 'Build' exceeded memory limit.` issue on the Test step? The yml config:
Please pay attention that no services is used.
Hello @Timur Aminev ,
Welcome to Atlassian Community!
The error "Container 'Build' exceeded memory limit." is returned when the commands you are executing as part of your step have exceeded the memory allocated to the build container where this step is running. Normal steps receive 4GB of memory, while large steps (size: 2x) have 8GB of available memory. This memory is shared with any services you are using in this step, so the actual value available to the Build Container might vary depending on the services you are using in the step (such as docker service, or a database, for example).
As you mentioned no services are being used (we cannot confirm from the screenshot as the pipelines definitions are collapsed), all the available memory for the step should be available for the Build container, and it seems like 8GB is not being sufficient for your tests to complete.
In such cases, I would suggest following the instruction covered in Troubleshooting Bitbucket Pipelines - Container Build exceeded memory limit to debug your pipelines and observe which process is consuming more memory.
In case you identify you need more than 8GB of memory, an alternative is to run the build in your own infrastructure by using self-hosted runners, where you can configure up to 32GB of memory (size: 8x).
Let me know in case you have any questions.
Thank you, @Timur Aminev .