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

Docker agent in declarative pipeline failing to login to custom registry

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • docker-workflow-plugin
    • Jenkins 2.124
      Docker Commons 1.13
      Docker Workflow 1.17

      We have an image that is stored in AWS ECR. Previously this step has been working but broke when we updated the Docker Workflow plugin from 1.15.1 to 1.17. We now get a `docker login failed` message.

      This is for a declarative pipeline and our configuration is as follows.

      stage('Docker step') {
           agent {
               docker {
                   image "xxxxxxxx"
                   registryUrl "https://xxxxxxxxx.dkr.ecr.us-east-1.amazonaws.com"
                   registryCredentialsId "credentials-id"
               }
           }
       }

      When we roll the plugin back to 1.15.1 the issue no longer occurs.
      This may be related to JENKINS-38018

          [JENKINS-51949] Docker agent in declarative pipeline failing to login to custom registry

          Daniel Fosbery created issue -
          Daniel Fosbery made changes -
          Description Original: We have an image that is stored in AWS ECR. Previously this step has been working but broke when we updated the Docker Workflow plugin from 1.15.1 to 1.17. We now get a `docker login failed` message.

          This is for a declarative pipeline and our configuration is as follows.

          ```
          stage('Docker step') \{
              agent \{
                  docker \{
                      image "xxxxxxxx"
                      registryUrl "https://xxxxxxxxx.dkr.ecr.us-east-1.amazonaws.com"
                      registryCredentialsId "credentials-id"
                  }
              }
          }
          ```
          When we roll the plugin back to 1.15.1 the issue no longer occurs.
          This may be related to JENKINS-38018
          New: We have an image that is stored in AWS ECR. Previously this step has been working but broke when we updated the Docker Workflow plugin from 1.15.1 to 1.17. We now get a `docker login failed` message.

          This is for a declarative pipeline and our configuration is as follows.
          {code:java}
          stage('Docker step') {
               agent {
                   docker {
                       image "xxxxxxxx"
                       registryUrl "https://xxxxxxxxx.dkr.ecr.us-east-1.amazonaws.com"
                       registryCredentialsId "credentials-id"
                   }
               }
           }{code}

           When we roll the plugin back to 1.15.1 the issue no longer occurs.
           This may be related to -JENKINS-38018-
          Ivan Fernandez Calvo made changes -
          Link New: This issue is related to JENKINS-51615 [ JENKINS-51615 ]
          Jesse Glick made changes -
          Link New: This issue relates to JENKINS-38018 [ JENKINS-38018 ]

            Unassigned Unassigned
            danielfosbery Daniel Fosbery
            Votes:
            6 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated: