How to disable the Docker Runner feature globally in Bamboo

Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.

Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible

Purpose

Bamboo 6.4 introduced a new feature, Docker Runner which allows a job to be executed within a Docker container rather than directly within the agent environment. It's enabled by default but this guide will show you how to disable it globally on your Bamboo instance.

Once disabled:

  • The UI tab, Job Configuration > Docker will no longer be accessible.

  • Bamboo Specs with Docker Runner config will be rejected on publish.

  • Any existing jobs that have been configured to run with Docker Runner will revert back to standard agent environment builds when executed.

Solution

There's a system property you can supply to Bamboo to completely disable Docker Runner:

  1. Edit your <bamboo-install>/bin/setenv.sh

    1. See Configuring your system properties for other methods of configuring system properties for Windows installations.

  2. Add the argument -Dbamboo.docker.pipelines.disable=true to your JVM_SUPPORT_RECOMMENDED_ARGS. Example:

    1 : ${JVM_SUPPORT_RECOMMENDED_ARGS:="-Dbamboo.docker.pipelines.disable=true"}
  3. Restart Bamboo

Updated on April 15, 2025

Still need help?

The Atlassian Community is here for you.