Skip to content

Allow to bind mount workspace and layers directories #2565

@myatmin

Description

@myatmin

Description

Make Pack CLI more CI-friendly for environments with strict mount path requirements, such as Bitbucket Pipelines.

Proposed solution

Add an option to prevent Pack CLI from creating named volumes for the workspace and layers directories.

Additional context

Understand that using the workspace directory this way may result in files being deleted. Users should copy any required workspace files before the directory is bind-mounted.

Host Settings:
  Binds: /opt/atlassian/pipelines/agent/build/web/target/dist:/workspace:rw
         /opt/atlassian/pipelines/agent/build/.cnb-cache/layers:/layers:rw
         /opt/atlassian/pipelines/agent/build/.cnb-cache/build/build-cache/build-cache:/cache
         /var/run/docker.sock:/var/run/docker.sock
         /opt/atlassian/pipelines/agent/build/.cnb-cache/launch/launch-cache:/launch-cache
         pack-layers-djjwvrfceo:/layers
         pack-app-kajizcksop:/workspace
  Network Mode: pack.local-network-6e7667706e6e6e6a7975

ERROR: failed to build: executing lifecycle: failed to create 'creator' container: Error response from daemon: authorization denied by plugin pipelines: -v only supports $BITBUCKET_CLONE_DIR and its subdirectories

Metadata

Metadata

Assignees

No one assigned

    Labels

    status/triageIssue or PR that requires contributor attention.type/enhancementIssue that requests a new feature or improvement.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions