I have a similar issue to this question but I have tried the suggested solutions and volume mounting still does not work.
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??
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
The “-v” option for mounting volumes doesn’t exist on docker-compose, only on docker itself.
Check your docker-compose.yml file for other volume mounting directives which may be clashing with the Bitbucket limitations.
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!
Beginning on April 4th, we will be implementing push limits. This means that your push cannot be completed if it is over 3.5 GB. If you do attempt to complete a push that is over 3.5 GB, it will fail...