Renovate-scan 0.4.1 works, but version 0.7.0 not

Rafael Grisotto_sb1yx4

Hi,

 

using version 0.4.1 of renovate-scan, the pipeline works, but not with version 0.7.0.

It is using the recommended configurations:

 

options:

  docker: true

  size: 2x

definitions:

  docker:

    memory: 7128

 

When switching to version 0.7.0, it fails with the error "Container 'docker' exceeded memory limit."

Theodora Boudale

Hi Rafael,

The error message means that the Docker service requires more than the currently allocated memory. Version 0.4.1 and version 0.7.0 of the pipe use a different Docker image, and it looks like the latest version may require more memory.

The definition for the memory of the Docker service needs to be as follows:

definitions:
  services:
    docker:
      memory: 7128

The definition you shared here is missing the services: part. Can you please check your bitbucket-pipelines.yml file and in case it is missing, add it as per the example I shared above?

If the definition is correct, this means that the 7128 MB allocated to the Docker service are not enough for the pipe to run. In this case, you'd need a larger step size (4x or 8x) and then allocate more memory to the Docker service.

I also wanted to point out that the options you have enabled in your bitbucket-pipelines.yml file will make all steps of all pipelines have a size of 2x and will enable the docker service in every step. If this is what you want, then no problem. Otherwise, if you don't need a 2x size or a docker service in every step, you can use step-level definitions instead:

• https://support.atlassian.com/bitbucket-cloud/docs/step-options/#Size
• https://support.atlassian.com/bitbucket-cloud/docs/step-options/#Services

Kind regards,
Theodora