docker-compose up fails because volumes source is outside repo, but it isn't

Kenneth Bingham_0s8l4e

 

<span>ERROR: for datadb Cannot create container for service datadb: authorization denied by plugin pipelines: -v only supports $BITBUCKET_CLONE_DIR</span>

 

<span>docker-compose.yml has</span>

<span>&nbsp;volumes:<br>- ./sql:/docker-entrypoint-initdb.d</span>

<span>and so it attempting to do the equivalent of </span>

<span>docker run -v $BITBUCKET_CLONE_DIR/sql:/docker-entrypoint-initdb.d<br></span>

 

I'm not able to reproduce this outside of Pipelines, by the way. docker-compose and Engine CLI can mount the same volume when running on my workstation and I have verified that the volume source directory is inside the Git working copy (clone dir).

 

<span>docker run -p 3306:3306 -d -e MYSQL_ROOT_PASSWORD=testpass -e MYSQL_DATABASE=testdb -v $BITBUCKET_CLONE_DIR/data/sql:/docker-entrypoint-initdb.d mysql:5.7</span>

<span>docker: Error response from daemon: authorization denied by plugin pipelines: -v only supports $BITBUCKET_CLONE_DIR.</span>

  

Kenneth Bingham_0s8l4e

BB confirmed they'd introduced a new security policy that excluded this use case (mounting a subtree of the repo working copy as a volume), and then apparently reverted that policy because this problem suddenly stopped presenting the following day.