I am currently trying to build a bitbucket pipeline which is supposed to run a docker-compose file to test a microservice before deployment. The docker compose file is supposed to build my microservice image and run it. This all seems to work fine locally, however, when I move things to the pipeline I constantly keep getting this error: #1 [internal] booting buildkit #1 pulling image moby/buildkit:buildx-stable-1 #1 pulling image moby/buildkit:buildx-stable-1 2.4s done #1 creating container buildx_buildkit_default 0.0s 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 Dockerfile FROM node:12-alpine WORKDIR /app/playground RUN npm install npm@7.1.2 RUN rm -rf /usr/local/lib/node_modules/npm RUN mv node_modules/npm /usr/local/lib/node_modules/npm COPY package.json package-lock.json ./ RUN npm ci COPY . . CMD [ "npm" , "run" , "start" ] docker-compose.yml version: "3" services: playground: build: . ports: - 9111 :9111 env_file: - ./envs/test.env I understand that bitbucket pipelines have some mechanism to prevent certain operations from executing for security reasons, but as far as I am aware I am not doing that here. Any idea of how I could possibly fix this error?

Hi all Neither adding export DOCKER_BUILDKIT=0 nor editing $PATH in bitbucket pipelines worked for me. Anyone has a solution outside of these? I tried adding either one, and both of them at the same time and still did not resolve the problem. - export DOCKER_BUILDKIT=0- echo "BuildKit ${DOCKER_BUILDKIT}" - export USR=/usr/bin- export PATH=$USR:$PATH- echo "Path ${PATH}"But im still getting #1 [internal] booting buildkit 12 #1 pulling image moby/buildkit:buildx-stable-1 13 #1 pulling image moby/buildkit:buildx-stable-1 2.8s done 14 #1 creating container buildx_buildkit_default done 15 #1 ERROR: Error response from daemon: authorization denied by plugin pipelines: --privileged=true is not allowed 16 ------ 17 [internal] booting buildkit: 18 ------ 19 ERROR: Error response from daemon: authorization denied by plugin pipelines: --privileged=true is not allowed 20

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; } } }

Bitbucket pipelines authorization denied by plugin pipelines

Marian Terchila

I am currently trying to build a bitbucket pipeline which is supposed to run a docker-compose file to test a microservice before deployment. The docker compose file is supposed to build my microservice image and run it.

This all seems to work fine locally, however, when I move things to the pipeline I constantly keep getting 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 2.4s done</span>
<span>#1 creating container buildx_buildkit_default 0.0s 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>

Dockerfile

<span>FROM</span> <span>node:12-alpine</span>
<span>WORKDIR</span> <span>/app/playground</span>
<span>RUN</span> <span>npm</span> <span>install</span> <span>npm@7.1.2</span>
<span>RUN</span> <span>rm</span> <span>-rf</span> <span>/usr/local/lib/node_modules/npm</span>
<span>RUN</span> <span>mv</span> <span>node_modules/npm</span> <span>/usr/local/lib/node_modules/npm</span>
<span>COPY</span> <span>package.json</span> <span>package-lock.json</span> <span>./</span>
<span>RUN</span> <span>npm</span> <span>ci</span>
<span>COPY</span> <span>.</span> <span>.</span>
<span>CMD</span> [ <span>"npm"</span>, <span>"run"</span>, <span>"start"</span> ]

docker-compose.yml

<span>version:</span> <span>"3"</span>
<span>services:</span>
  <span>playground:</span>
    <span>build:</span> <span>.</span>
    <span>ports:</span>
      <span>-</span> <span>9111</span><span>:9111</span>
    <span>env_file:</span>
      <span>-</span> <span>./envs/test.env</span>

I understand that bitbucket pipelines have some mechanism to prevent certain operations from executing for security reasons, but as far as I am aware I am not doing that here.

Any idea of how I could possibly fix this error?

Accepted answers

All comments

Alexander Prams_lb0utk

I'm currently having the same error, could you resolve it?

Marian Terchila

I have managed to find a working solution to this.

Instead of using build: . in your docker-compose.yml, build the image from the Dockerfile as part of the pipeline and use that image tag in your docker-compose.yml

docker-compose.yml becomes

version: "3"

services:

cases-ms:

image: cases-ms

pipeline becomes

- step:

name: Unit tests and Snyk scan

image: alpine:3.12

runs-on:

- self.hosted

- linux

services:

- docker

script:

- apk add nodejs npm curl

- curl -SL https://github.com/docker/compose/releases/download/v2.11.2/docker-compose-linux-x86_64 -o /usr/local/bin/docker-compose

- chmod +x /usr/local/bin/docker-compose

- echo //registry.npmjs.org/:_authToken=$NPM_TOKEN_READ_ONLY >> .npmrc

- docker build . -t $BITBUCKET_REPO_SLUG

Alexander Prams_lb0utk

Thanks for the followup! I actually also resorted to building with docker build but am also running my 3 containers with docker run separately now, so I was basically rebuilding docker-compose. That was feasible for just 3 containers, but yeah.

I will try your approach as well

wrc92

I was able to get a docker-compose build working by adding this at the beginning of my script:

- export DOCKER_BUILDKIT=0

Stephan Hohn_osanf4

Added

DOCKER_BUILDKIT=0

as build/repository variable

Alessandro Muraro

Thanks Stephan

Rich Kalsky

I too was getting this error:

+ docker build --build-arg SSH_PRIVATE_KEY -t $IMAGE_NAME .
WARNING: No output specified with docker-container driver. Build result will only remain in the build cache. To push result image into registry use --push or to load image into docker use --load
#1 [internal] booting buildkit
#1 pulling image moby/buildkit:buildx-stable-1
#1 pulling image moby/buildkit:buildx-stable-1 3.4s done
#1 creating container buildx_buildkit_default 0.0s done
#1 ERROR: Error response from daemon: authorization denied by plugin pipelines: --privileged=true is not allowed
------
> [internal] booting buildkit:
------
ERROR: Error response from daemon: authorization denied by plugin pipelines: --privileged=true is not allowed

So I added the "export DOCKER_BUILDKIT=0" and that allowed it to build, BUT it says it's deprecated. So now what do I need to do to future-proof my pipeline?

+ docker build --build-arg SSH_PRIVATE_KEY -t $IMAGE_NAME .
bash: warning: command substitution: ignored null byte in input
bash: warning: command substitution: ignored null byte in input
DEPRECATED: The legacy builder is deprecated and will be removed in a future release.
BuildKit is currently disabled; enable it by removing the DOCKER_BUILDKIT=0
environment-variable.

unknown

Somarjun Chandolu_5rzjho

Mark Bence Kiss

Same here!

Tuomas Pesola_vc4p2m

Same here. Any suggestions?

Sean Sedman

Adding export DOCKER_BUILDKIT=0 to the build pipeline resolved my issue but as already mentioned in a previous comment, the legacy builder is deprecated and will be removed eventually.

More information about BuildKit can be found in the Docker Documentation.

Fabio Parlascino

Suddenly having the same issue.

Andreas F_w6n2yp

Thanakorn Khuntum

I had the same problem 14 days ago still working.

Thanakorn Khuntum

OMG

add

- export DOCKER_BUILDKIT=0

in bitbucket-pipelines.yml

- export DOCKER_BUILDKIT=0

- docker build -t ...

it working for me

Patrick Nelson

Check out Theodora's solution (from Atlassian) in this answer here: https://community.atlassian.com/t5/Bitbucket-questions/Re-Docker-build-failing-for-buildkit-with-error-authori/qaq-p/2381177/comment-id/94515#M94515

Basically, another good solution might be to update the $PATH to point to /usr/bin so you don't have to manually disable BuildKit (especially useful if the legacy builder ever ends up going away, possibly breaking things again).

Takudzwa Shumbamhini_8vduex

Hi all

Neither adding export DOCKER_BUILDKIT=0 nor editing $PATH in bitbucket pipelines worked for me. Anyone has a solution outside of these? I tried adding either one, and both of them at the same time and still did not resolve the problem.

- export DOCKER_BUILDKIT=0

- echo "BuildKit ${DOCKER_BUILDKIT}"

- export USR=/usr/bin

- export PATH=$USR:$PATH

- echo "Path ${PATH}"

But im still getting

#1 [internal] booting buildkit

#1 pulling image moby/buildkit:buildx-stable-1

#1 pulling image moby/buildkit:buildx-stable-1 2.8s done

#1 creating container buildx_buildkit_default done

<span>#1 ERROR: Error response from daemon: authorization denied by plugin pipelines: --privileged=true is not allowed</span>

------

 [internal] booting buildkit:

------

<span>ERROR: Error response from daemon: authorization denied by plugin pipelines: --privileged=true is not allowed</span>

Daniel Engelhardt_nayb7m

For anybody who stumbles upon this, my issue was that I was trying to mount a named volume to one of my containers, which apparently isn't allowed in bitbucket.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

bitbucket

bitbucket-cloud

bitbucket-pipelines