Pipeline: Container 'docker' exceeded memory limit (Vuejs)

[Adan J. Suarez]

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

[jeromemiranda]

Have the same issue, already using 

      options:    

           size: 2x

and

      definitions:    

            services:        

                   docker:            

                        memory: 6144 

but still the same problem

[pritij]

@Adan J. Suarez  did you find any solution for the memory issue?

In our case, the build fails at npm run build step.

[Adan J. Suarez]

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!

[Antoine Büsch]

Hi Adan,

at which point exactly is the error occuring? Is it when calling the pipe?

Cheers,

Antoine

[Adan J. Suarez]

Not, it is when building the container image.