Your builds fail when pushing images to Amazon ECR encountering a
ProcessException: Error executing '/usr/bin/docker login -u AWS -p ******** -e ********
', exit code: 125:
You are probably using Utoolity's ECR Credentials task together with Atlassian's built-in Docker task, as outlined in How to push a Docker image to a repository in your Amazon ECR registry with the Bamboo Docker task.
Under the hood, the Bamboo Docker task is using a docker login command line including the meanwhile unsupported --email or -e flag, as confirmed by the resp. issue Docker Task: -e required for docker push command (BAM-18613). The --email or -e flag has been removed as of Docker version 17.06.0-ce, so an upgrade to this or a newer Docker version without an accompanying upgrade of the Bamboo Docker task will yield the exception at hand.
You should upgrade to a newer Bamboo release that addresses this problem - according to Docker Task: -e required for docker push command (BAM-18613) the first version that includes this fix seems to be 6.2.0.
If you cannot upgrade your Bamboo version right away, you might be able to apply one of the following workarounds:
Upgrade only the Bamboo Docker app itself to release 6.2.0, as suggested by Atlassian's Alexey Chystoprudov in his answer to Bamboo Docker Push fails
Please note that Alexey emphasizes that they cannot guarantee it is 100% compatible!
Temporarily replace the dedicated Docker task by specifying the desired docker login command line without the --email flag from a Script task instead.
You can inject the ECR credentials in a similar fashion as outlined for the regular AWS credentials in How to work around limitations with the AWS Command Line Interface (AWS CLI).