-
Notifications
You must be signed in to change notification settings - Fork 5.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Bind mounts no longer work in Bitbucket Pipelines in v2.29.3 #12121
Comments
I meet the same issue My with docker-compose.yml:
but with v2.29.2 directory "/var/lib/mysql" will auto create. |
mount API exists in docker engine for a while, I wonder it is not supported by bitbucket. The bind API is legacy which comes with many limitations. We rely on mount API as compose file syntax offers fine grained support of bind mounts which is only available with this newer API. @phuongl-ampere can you please open a dedicated issue ? |
We had to pin the image in the runner to docker:27.1.2 wich runs the older compose. Until bitbucket sorts their end in 2027 (or circa) hahahaha |
Can you test with the latest |
Confirmed fixed in v2.29.7 :) |
Description
First of all, apologies for the framing here - I don't know enough about the Docker API to understand what the real problem is here, and calling this a bug is probably wrong.
Since upgrading our pipelines runner image to use compose v2.29.3, attempting to run a compose configuration that uses bind mounts in Bitbucket Pipelines is producing this error:
Error response from daemon: authorization denied by plugin pipelines: --mounts is not allowed
I'm guessing the relevant change here is #12078, and the problem is that compose has switched to using a new API for mounts that Bitbucket does not support.
Is there a way to revert to using the old API for bind mounts? Or do we just need to pin v2.29.2 for the foreseeable future?
Steps To Reproduce
Push to a Bitbucket Cloud repository.
Compose Version
Docker Environment
Anything else?
No response
The text was updated successfully, but these errors were encountered: