Uploaded image for project: 'Bitbucket Cloud'
  1. Bitbucket Cloud
  2. BCLOUD-21719

Custom pipes pulled from a docker registry where a port number is specified fail to run.

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Low Low
    • Pipelines - Pipes
    • None

      Issue Summary

      Pipes that are fetched from Docker registries where a port number is provided will fail to start.

       

      Steps to Reproduce

      An example pipeline:

      pipelines:
  default:
    - step:
      name: Test pipes from dockerhub with port
      script:
        - pipe: docker://registry.hub.docker.com:443/bitbucketpipelines/demo-pipe-bash

      This was reported via the community at https://community.atlassian.com/t5/Bitbucket-questions/Pipes-in-private-repository-with-a-port-number-cannot-run-on/qaq-p/1935450

      Expected Results

      The pipe can be executed.

      Actual Results

      The pipe fails with the following error:

      Status: Downloaded newer image for registry.hub.docker.com:443/bitbucketpipelines/demo-pipe-bash:latestdocker: Error response from daemon: invalid volume specification: '/opt/atlassian/pipelines/agent/build/.bitbucket/pipelines/generated/pipeline/pipes/registry.hub.docker.com:443/bitbucketpipelines/demo-pipe-bash:/opt/atlassian/pipelines/agent/build/.bitbucket/pipelines/generated/pipeline/pipes/registry.hub.docker.com:443/bitbucketpipelines/demo-pipe-bash'.See 'docker run --help'.

      Workaround

      None yet, we will need to deploy a fix to allow pipes using arbitrary port numbers to be run.

              jsgreccia@atlassian.com Joao Sgreccia (Inactive)
              ggatus Graham Gatus
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: