aws-toolkit-azure-devops icon indicating copy to clipboard operation
aws-toolkit-azure-devops copied to clipboard

src/tasks/ECRPushImage failed pipeline step

Open mauricioreinbold opened this issue 10 months ago • 1 comments

Describe the bug

While deploying a windows-2022 Image with Azure Pipelines 2 Agent the ECR Push Image task pipeline step fails.

Expected behavior

Mentioned pipeline step works with Windows pushes to ECR.

Logs

Invoking 'C:\Windows\system32\docker.exe' with command 'login' ##[debug]which 'C:\Windows\system32\docker.exe' ##[debug]found: 'C:\Windows\system32\docker.exe' ##[debug]C:\Windows\system32\docker.exe arg: login ##[debug]C:\Windows\system32\docker.exe arg: -u ##[debug]C:\Windows\system32\docker.exe arg: AWS ##[debug]C:\Windows\system32\docker.exe arg: -p ##[debug]C:\Windows\system32\docker.exe arg: xxx ##[debug]C:\Windows\system32\docker.exe arg: https://472662001309.dkr.ecr.eu-central-1.amazonaws.com/ ##[debug]exec tool: C:\Windows\system32\docker.exe ##[debug]arguments: ##[debug] login ##[debug] -u ##[debug] AWS ##[debug] -p ##[debug] xxx ##[debug] https://472662001309.dkr.ecr.eu-central-1.amazonaws.com/ ##[debug]Process exited with code 1 and signal null for tool 'C:\Windows\system32\docker.exe' ##[debug]STDIO streams have closed and received exit code 1 and signal null for tool 'C:\Windows\system32\docker.exe' ##[debug]task result: Failed ##[error]Error: The process 'C:\Windows\system32\docker.exe' failed with exit code 1 ##[debug]Processed: ##vso[task.issue type=error;source=TaskInternal;]Error: The process 'C:\Windows\system32\docker.exe' failed with exit code 1 ##[debug]Processed: ##vso[task.complete result=Failed;]Error: The process 'C:\Windows\system32\docker.exe' failed with exit code 1

Your Environment

  • Cloud based
  • AWS Toolkit for Azure DevOps version: 1.18.0

Additional context

mauricioreinbold avatar Jan 15 '25 11:01 mauricioreinbold

Hi there! Having the same issue here! Were you able to solve it? I was trying to get the code recreated in powershell with the 'AWSPowerShellModuleScript@1' but it is a bit painful, getting 400's no matter what.

tupenieks avatar Mar 31 '25 13:03 tupenieks