Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-63264

Docker Pipeline: Hardcoded requirement to prefix registry with https:// doesn't work with Nexus

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      When creating a Multibranch Pipeline job (or globally in Jenkins configuration), it is possible to specify an alternate Docker registry to pull images from. Unfortunately, the input field considers URLs w/o "https://" prefix as invalid, which is wrong if the registry is hosted on a Sonatype Nexus repository server or in AWS ECR. In this case the registry must be provided as either <hostname>:<port> (Nexus) or just <hostname> (AWS ECR), but this is not accepted.

      However, it's working fine when using Docker commands directly, for example:

      docker login <hostname>:<port>

      or

      docker push <hostname>:<port>/<image>:<tag>

      Please fix the plugin so that it works with above Docker registries.

        Attachments

          Activity

          dhs Dirk Heinrichs created issue -
          dhs Dirk Heinrichs made changes -
          Field Original Value New Value
          Description When creating a Multibranch Pipeline job (or globally in Jenkins configuration, it is possible to specify an alternate Docker registry to pull images from. Unfortunately, the input field considers URLs w/o "https://" prefix as invalid, which is wrong if the registry is hosted on a Sonatype Nexus repository server or in AWS ECR. In this case the registry must be provided as either <hostname>:<port> (Nexus) or just <hostname> (AWS ECR), but this is not accepted.

          However, it's working fine when using Docker commands directly, for example:
          {code:java}
          docker login <hostname>:<port>{code}
          or
          {code:java}
          docker push <hostname>:<port>/<image>:<tag>{code}
          Please fix the plugin so that it works with above Docker registries.
          When creating a Multibranch Pipeline job (or globally in Jenkins configuration), it is possible to specify an alternate Docker registry to pull images from. Unfortunately, the input field considers URLs w/o "https://" prefix as invalid, which is wrong if the registry is hosted on a Sonatype Nexus repository server or in AWS ECR. In this case the registry must be provided as either <hostname>:<port> (Nexus) or just <hostname> (AWS ECR), but this is not accepted.

          However, it's working fine when using Docker commands directly, for example:
          {code:java}
          docker login <hostname>:<port>{code}
          or
          {code:java}
          docker push <hostname>:<port>/<image>:<tag>{code}
          Please fix the plugin so that it works with above Docker registries.
          dhs Dirk Heinrichs made changes -
          Summary Docker Pipeline: Hardcoded requirements to prefix registry with https:// doesn't work with Nexus Docker Pipeline: Hardcoded requirement to prefix registry with https:// doesn't work with Nexus

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            dhs Dirk Heinrichs
            Votes:
            1 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated: