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

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

---
Originally reported by danielfosbery, imported from: Docker agent in declarative pipeline failing to login to custom registry

• status: Open
  
• priority: Major
  
• component(s): docker-workflow-plugin
  
• label(s): docker, plugin
  
• resolution: Unresolved
  
• votes: 6
  
• watchers: 7
  
• imported: 2025-12-07
  

Raw content of original issue

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

environment

```
Jenkins 2.124

Docker Commons 1.13

Docker Workflow 1.17
```