You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We've started experiencing failures to login to AWS ECR starting from windows-2022 20241211.1.0
We're using "big" runners, which have received the update to 20241211.1.0 on which we're experiencing this failure.
We're not experiencing this on windows-2022 runners, which still have 20241201.2.0
Platforms affected
Azure DevOps
GitHub Actions - Standard Runners
GitHub Actions - Larger Runners
Runner images affected
Ubuntu 20.04
Ubuntu 22.04
Ubuntu 24.04
macOS 12
macOS 13
macOS 13 Arm64
macOS 14
macOS 14 Arm64
macOS 15
macOS 15 Arm64
Windows Server 2019
Windows Server 2022
Image version and build link
Works as expected in 20241201.2.0
fails in 20241211.1.0
Is it regression?
20241201.2.0
Expected behavior
I'm able to authenticate with AWS ECR using aws-actions/amazon-ecr-login@v1
Actual behavior
Error: Could not login to registry redacted.dkr.ecr.eu-west-1.amazonaws.com: WARNING! Using --password via the CLI is insecure. Use --password-stdin.
Error saving credentials: error storing credentials - err: exit status 1, out: `A specified logon session does not exist. It may already have been terminated.`
We have a similar issue moving from 20241202.1.0 to 20241211.2.0 where executing docker login fail to save credentials:
Run docker/login-action@v3
Logging into us-docker.pkg.dev/XXXXXXXXX...
Error: Error saving credentials: error storing credentials - err: exit status 1, out: `The stub received bad data.`
Description
We've started experiencing failures to login to AWS ECR starting from windows-2022 20241211.1.0
We're using "big" runners, which have received the update to 20241211.1.0 on which we're experiencing this failure.
We're not experiencing this on windows-2022 runners, which still have 20241201.2.0
Platforms affected
Runner images affected
Image version and build link
Works as expected in 20241201.2.0
fails in 20241211.1.0
Is it regression?
20241201.2.0
Expected behavior
I'm able to authenticate with AWS ECR using aws-actions/amazon-ecr-login@v1
Actual behavior
Repro steps
The text was updated successfully, but these errors were encountered: