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
Next: Root
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
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hello everyone:
I've been fighting with this problem for three days already. The thing is, I have a pipeline to deploy my container in AWS ECR and it fail saying: Container 'docker' exceeded memory limit, when I push my master branch.
It is a frontend in Vuejs with a Nginx server, as it is recommended in Vue documentation, it is not big and I assigned - I think - enough resources.
I've been trying different memory configuration, in size: 1x and 2x and, memory: 1024, 2048... 7128. And none of them works. It build in my end.
Any idea other than memory? I think I tried all combinations.
The following is my `bitbacket-pipeline.yml`:
image: node:12
pipelines:
default:
- step:
size: 1x
caches:
- node
script:
- npm install
- npm run test:unit
branches:
master:
- step:
size: 2x
caches:
- node
script:
- npm install
- npm run test:unit
# Build the image.
- docker build -t beautiful-frontend .
# use the pipe to push the image to AWS ECR
- pipe: atlassian/aws-ecr-push-image:1.0.2
variables:
AWS_ACCESS_KEY_ID: $AWS_ACCESS_KEY_ID
AWS_SECRET_ACCESS_KEY: $AWS_SECRET_ACCESS_KEY
AWS_DEFAULT_REGION: $AWS_DEFAULT_REGION
IMAGE_NAME: beautiful-frontend
services:
- docker
definitions:
service:
docker:
# Memory docker-in-docker
memory: 7128
Have the same issue, already using
options:
size: 2x
and
definitions:
services:
docker:
memory: 6144
but still the same problem
@Adan J. Suarez did you find any solution for the memory issue?
In our case, the build fails at npm run build step.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes, I did. In our Dockerfile we changed as follow:
(original):
FROM node:12
(new version):
FROM node:12-alpine
The alpine version is smaller and that solved the problem. Hope that helps!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This solved my problem that I had in Azure Static Web Apps (azure-static-web-apps-deploy). Thanks!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Adan,
at which point exactly is the error occuring? Is it when calling the pipe?
Cheers,
Antoine
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.