Add support for Docker Compose named volumes

Issue #17592 open
Jeroen De Raedt
staff created an issue

The Docker authorization plugin currently doesn't support named volumes for Docker compose (see https://docs.docker.com/compose/compose-file/#volumes). As a result, mappings to named volumes are being treated as absolute paths and subsequently error.

A workaround is to create and map and empty directory and attach it to both containers.

Comments (2)

  1. Thijs Daniels

    I'm not sure if this comment is helpful, since I know nothing about Pipelines' internals, but, assuming this auth check happens before the compose command is run and involves parsing the docker-compose.yml, it might be enough to check if the volume's source parameter matches a key in the volumes array. If it does, docker-compose will treat it as a named volume.

  2. Aneita Yang staff
    • changed status to open

    Thanks for the suggestion.

    Given the team is currently working on higher priority projects, it's unlikely that we'll work on this anytime soon. In the meantime, however, I'll open this ticket to gauge the interest of other users on this feature.

  3. Log in to comment