Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Pipeline service is started although not requested

Vincent Botteman
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
October 1, 2025

In bitbucket-pipelines.yml, I've specified docker service with an allowed memory of 2Gb. 

If I run a custom pipeline, then according to the metrics, the docker service is started although that service is not specified in the definition of the custom pipeline.

It seems the docker service is always started. Can I reduce the allowed memory in my custom pipeline? I only need 2 Gb for two specific pipelines.

1 answer

1 accepted

0 votes
Answer accepted
Ben
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
October 2, 2025

Hi @Vincent Botteman 

The docker service is only started if it's explicitly referenced in your build step. This is indicated by a Docker tab present in the build logs.

For example: 

The following build will not have the docker service enabled:

definitions: 
  services:
    docker:
        memory: 2048

pipelines:
   branches:
      master:
           - step:
                 name: 'Echo Message'
                 script:
                 - echo "Welcome to Bitbucket Pipelines!"


This build will have the docker service enabled, however, as the service is being specifically called in the step itself:

 

definitions: 
  services:
    docker:
        memory: 2048

pipelines:
   branches:
      master:
           - step:
                 name: 'Echo Message'
                 script:
                 - echo "Welcome to Bitbucket Pipelines!"
services:
- docker


 

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
TAGS
AUG Leaders

Atlassian Community Events