Bitbucket pipelines: How can I share a volume between two containers using Docker Compose?

Eugenio Carocci

Hi all,

 

I'd like to understand if there's a way to share a volume, in the Bitbucket pipeline context, between two containers defined in a `docker-compose` cluster at version 3.*.

 

To let everybody better understand my issue I have a `docker-compose.yml` like this:

version: "3.7"
# --------- #
# Services  #
# --------- #
services:
###########
  # PHP-FPM #
  ############
  php-fpm:
image: custom/php-fpm
volumes:
      - app-data:/var/www/html
  ######################
  # Apache Application #
  ######################
  www:
image: custom/apache
depends_on:
      - php-fpm
volumes:
      - app-data:/var/www/html
# --------- #
# Volumes   #
# --------- #
volumes:
app-data:

This is obviously a super simplification of my scenario.

 

Anyway, the key issue is that I'm not able to share the `app-data` volume since Bitbucket gives the following error:

"ERROR: for app-pipelines_php-fpm_1  Cannot create container for service php-fpm: authorization denied by plugin pipelines: -v only supports $BITBUCKET_CLONE_DIR and its subdirectories
ERROR: for php-fpm  Cannot create container for service php-fpm: authorization denied by plugin pipelines: -v only supports $BITBUCKET_CLONE_DIR and its subdirectories"

 

Thanks for your time

 

Eugenio

Taras Postument

Hey, I faced the same problem and ended up with the following hack.

Instead of defining the global volume (like your `app-data:`) I used dynamic volumes definition with the `BITBUCKET_CLONE_DIR` dir variable.

This way, when composing is running in the BB Pipeline volume is mounted int `BITBUCKET_CLONE_DIR` and when I run it locally, the standard volume is created.

- &static_volume ${BITBUCKET_CLONE_DIR:-static}:/usr/src/app/static

Then you can use it like

volumes: 
- *static_volume

In all the container definitions.

 

Also, I unsuccessfully tried other workarounds like:

volumes:
  static:
    driver: local
    driver_opts:
      type: none
      o: bind
      device: ${BITBUCKET_CLONE_DIR:-/tmp}

or

volumes:
  static:
    driver: local
    driver_opts:
      type: tmpfs
      device: tmpfs

 

While both worked locally, none worked in the Pipeline.

Hope it helps!