Bitbucket "Allocated memory" Exceeded for Services

By Kaveh Alemi·Latchkey

You asked services for more memory than the step has to give. Each step has a total memory budget shared between the build container and every service; the sum cannot exceed it.

What this error means

The pipeline fails configuration or startup with a message that the total memory requested for services exceeds the available step memory, or that a service exceeded its allocation. It surfaces as soon as the step tries to start its services.

The total memory allocated for services (4096 MB) exceeds the
available memory for the step. Increase the step size or reduce
service memory.

Common causes

Service memory sums above the step budget

A 1x step has a fixed total. The build container reserves part of it; whatever is left is all the services can share. Requesting more across services overcommits the step.

A single service requests too much

One service with a large memory: value can leave too little for the build container, or exceed the per-step ceiling outright.

How to fix it

Increase the step size

A 2x step roughly doubles the total memory pool, giving services more room.

- step:
    size: 2x
    services: [ postgres, redis ]
    script: [ ./test.sh ]

Lower per-service memory requests

Trim each service memory: so the total (plus the build container reserve) fits the step budget.

definitions:
  services:
    postgres: { image: postgres:16, memory: 512 }
    redis:    { image: redis:7,     memory: 256 }

How to prevent it

• Add up service memory and keep it within the step budget minus the build reserve.
• Use 2x steps when running several services.
• Drop services you do not actually need in a given step.

Frequently asked questions

Related guides

References

• GitHub Actions documentation