-
Notifications
You must be signed in to change notification settings - Fork 173
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
no basic auth credentials #337
Comments
Facing the same issue too. |
Same issue when running multiple pushes on different actions on the same runner instance. |
Could you paste the exact error from your logs here, covering any sensitive information? |
Nothing really more useful than OP provided sadly :/
But I can easily reproduce it.
|
Could it be any of the issues mentioned here: https://docs.aws.amazon.com/AmazonECR/latest/userguide/common-errors-docker.html#error-403? |
Pretty sure it's not:
|
Got the same error for me in our GitHub self-hosted server having 3 runners in the same server. Can someone help? There is no issue with authentication creds with AWS. |
@RobinFrcd what was your workaround concerning this issue |
@nerdeveloper To have the 2 runners on 2 different instances ... |
OMG! I just knew it. but I thought you'd be able to make it work without having to do that. The solution to this is to increase costs. @arjraman, any time to fix this issue |
This is my workaround. I used the native docker login; you can use this if you choose to have multiple runners in one VM pending when this issue is fixed. - name: Login into ECR
run: echo ::set-output name=logged-in::$(aws ecr get-login-password --region us-west-1 | docker login --username AWS --password-stdin [private ECR repo URL]) |
Some time when pipeline fails with the below error:
no basic auth credentials
,it does not happens regularly but in every 10-15 days this issue is occurring.
Pipeline steps:
The text was updated successfully, but these errors were encountered: