I have a similar issue to this question but I have tried the suggested solutions and volume mounting still does not work. * I have verified that the directory I am trying to mount as a volume does exist within my build directory * I have run the `docker run ...` bare command with my container, which downloads and runs the container with no problems * I have tried using a volume mount with the environment variable, e.g. `docker run -v="$BITBUCKET_CLONE_DIR/dist:/dist" 18fgsa/html-proofer /dist` * I have also tried using a volume mount with the absolute path, e.g. `docker run -v="/opt/atlassian/pipelines/agent/build/dist:/dist" 18fgsa/html-proofer /dist` * I have also tried the volume mount option in the other format, e.g. `docker run -v "$BITBUCKET_CLONE_DIR/dist:/dist" 18fgsa/html-proofer /dist` All of these permutations have resulted in the same error: `docker: Error response from daemon: authorization denied by plugin pipelines: Command not supported.` Is there some permission which has not been enabled for Docker volume mounts??

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: does Docker volume mounting work yet?

Drew Robinson

I have a similar issue to this question but I have tried the suggested solutions and volume mounting still does not work.

I have verified that the directory I am trying to mount as a volume does exist within my build directory
I have run the `docker run ...` bare command with my container, which downloads and runs the container with no problems
I have tried using a volume mount with the environment variable, e.g. `docker run -v="$BITBUCKET_CLONE_DIR/dist:/dist" 18fgsa/html-proofer /dist`
I have also tried using a volume mount with the absolute path, e.g. `docker run -v="/opt/atlassian/pipelines/agent/build/dist:/dist" 18fgsa/html-proofer /dist`
I have also tried the volume mount option in the other format, e.g. `docker run -v "$BITBUCKET_CLONE_DIR/dist:/dist" 18fgsa/html-proofer /dist`

All of these permutations have resulted in the same error:

`docker: Error response from daemon: authorization denied by plugin pipelines: Command not supported.`

Is there some permission which has not been enabled for Docker volume mounts??

Accepted answers

Drew Robinson

Ok, for anyone reading this, as per the reply linked above, the answer is that you can currently only mount the bare $BITBUCKET_CLONE_DIR itself as the source for a volume. Any paths below it must be accounted for in your parameters passed to the run command.

So I changed my first example above to:

docker run -v="$BITBUCKET_CLONE_DIR:/app" 18fgsa/html-proofer /app/dist

... and then it worked.

Thanks @Philip Hodder

All comments

Drew Robinson

Aha, I've just seen this reply to a similar question, I'll try that and see if it works for my issue.

Drew Robinson

So I changed my first example above to:

docker run -v="$BITBUCKET_CLONE_DIR:/app" 18fgsa/html-proofer /app/dist

... and then it worked.

Thanks @Philip Hodder

Chris Gunnels

I've tried this solution but still running into the error. I'm running

docker-compose run -d -v="$BITBUCKET_CLONE_DIR:/my_app_name" service_name

What am I missing here?

Drew Robinson

What’s your exact error Chris? Because you’re using `docker-compose` instead of Docker as I was, you may be subject to different permissions.

Chris Gunnels

Hey Drew, I'm getting this error:

ERROR: for app_name_postgres Cannot create container for service db: authorization denied by plugin pipelines: -v only supports $BITBUCKET_CLONE_DIR and its subdirectories

dmoller

Additionally to only mounting BITBUCKET_CLONE_DIR, beware that files should be world-readable (I guess). That is chmod o+r.

In my case I was creating files with the mktemp tool and they would have 0600 permissions by default. They are fully operable from the pipeline script and permissions are not distinguishable once inside the subcontainer, but they will fail to be read!

Welcome!

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

Quick Links

Find more posts tagged with

bitbucket

bitbucket-pipelines

docker

volume