Compose is supposed to be supported. Buildkit is supposed to be supported. It seems buildkit and compose is not supported? Here is my compose file: version: "3.9" services: myservice: platform: linux/amd64 privileged: false # I also tried adding this image: someimage build: context: . dockerfile: "Dockerfile" secrets: - pypi_conf secrets: pypi_conf: file: "${BITBUCKET_CLONE_DIR}/pypi_config/pip/pip.conf" Here is my yaml file: image: atlassian/default-image:3 definitions: services: docker: memory: 3072 steps: - step: &build name: Build image: name: tiangolo/docker-with-compose script: - export DOCKER_BUILDKIT=1 - docker compose build services: - docker pipelines: default: - step: *build branches: master: - step: *build Im not mounting anything outside of the allowed BITBUCKET_CLONE_DIR. But I get this error: #1 [internal] booting buildkit #1 pulling image moby/buildkit:buildx-stable-1 #1 pulling image moby/buildkit:buildx-stable-1 3.1s done #1 creating container buildx_buildkit_default done #1 ERROR: Error response from daemon: authorization denied by plugin pipelines: --privileged=true is not allowed ------ > [ internal ] booting buildkit: ------ Error response from daemon: authorization denied by plugin pipelines: --privileged=true is not allowed make: *** [ Makefile:134: testing ] Error 17 Even if I remove the `secrets` mount config and keep ` DOCKER_BUILDKIT=1` I get this error. So is buildkit and compose together not supported for some reason? If I set ` DOCKER_BUILDKIT=0` I don't get a perms error, but I need that to mount secrets. All of this is supposed to be supported so I'm not understanding why I'm getting these errors.

nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Can't run compose in bitbucket pipelines getting --privileged=true is not allowed

red888

Compose is supposed to be supported.

Buildkit is supposed to be supported.

It seems buildkit and compose is not supported?

Here is my compose file:

<span>version:</span> <span>"3.9"</span>
<span>services:</span>
  <span>myservice:</span>
    <span>platform:</span> <span>linux/amd64</span>
    <span>privileged:</span> <span>false</span> <span># I also tried adding this</span>
    <span>image:</span> <span>someimage</span>
    <span>build:</span>
      <span>context:</span> <span>.</span>
      <span>dockerfile:</span> <span>"Dockerfile"</span>
      <span>secrets:</span>
        <span>-</span> <span>pypi_conf</span>

<span>secrets:</span>
  <span>pypi_conf:</span>
    <span>file:</span> <span>"${BITBUCKET_CLONE_DIR}/pypi_config/pip/pip.conf"</span>

Here is my yaml file:

<span>image:</span> <span>atlassian/default-image:3</span>

<span>definitions:</span>
  <span>services:</span>
    <span>docker:</span>
      <span>memory:</span> <span>3072</span>
  <span>steps:</span>
    <span>-</span> <span>step:</span> <span>&build</span>
        <span>name:</span> <span>Build</span>
        <span>image:</span>
          <span>name:</span> <span>tiangolo/docker-with-compose</span>
        <span>script:</span>
          <span>-</span> <span>export</span> <span>DOCKER_BUILDKIT=1</span>
          <span>-</span> <span>docker</span> <span>compose</span> <span>build</span>
        <span>services:</span>
          <span>-</span> <span>docker</span>
<span>pipelines:</span>
  <span>default:</span>
    <span>-</span> <span>step:</span> <span>*build</span>
  <span>branches:</span>
    <span>master:</span>
      <span>-</span> <span>step:</span> <span>*build</span>

Im not mounting anything outside of the allowed BITBUCKET_CLONE_DIR.

But I get this error:

<span>#1 [internal] booting buildkit</span>
<span>#1 pulling image moby/buildkit:buildx-stable-1</span>
<span>#1 pulling image moby/buildkit:buildx-stable-1 3.1s done</span>
<span>#1 creating container buildx_buildkit_default done</span>
<span>#1 ERROR: Error response from daemon: authorization denied by plugin pipelines: --privileged=true is not allowed</span>
<span>------</span>
 <span>></span> [<span>internal</span>] <span>booting buildkit:</span>
<span>------</span>
<span>Error response from daemon: authorization denied by plugin pipelines:</span> <span>--privileged=true</span> <span>is</span> <span>not</span> <span>allowed</span>
<span>make:</span> <span>***</span> [<span>Makefile:134:</span> <span>testing</span>] <span>Error</span> <span>17</span>

Even if I remove the `secrets` mount config and keep `DOCKER_BUILDKIT=1` I get this error. So is buildkit and compose together not supported for some reason?

If I set `DOCKER_BUILDKIT=0` I don't get a perms error, but I need that to mount secrets.

All of this is supposed to be supported so I'm not understanding why I'm getting these errors.

Accepted answers

All comments

Sander Mol_4waiwv

Encountered the same, might this have to do with the buildx driver that seems to be used by default? Atlassian does not allow running `privileged` containers within a pipeline, and it seems this is exactly how the build container (`--driver docker-container`) seems to work.

It might be solved if someone can give directions on how to use the option to not have this build container (`--driver docker`), so the `privileged` container will not be spawned at all.

Anyone from Atlassian might be able to give more feedback? Might this be a default Docker Deamon setting?

Seth Miller

So BuildKit support is just completely broken?

Rich Kalsky

Did you get any replies/answers for this?

Aymen Toukabri

is there any updates ?

Gianpietro Basei

Hi, I doubt this will ever change; We are currently building each service separately (without using compose)