-
Notifications
You must be signed in to change notification settings - Fork 32
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
Resolve failed Docker deployments with credentials #655
Comments
^^ this appears to be the solution. Thanks @gcoxmoz |
@smarnach This is the situation |
rtucker-mozilla
pushed a commit
to rtucker-mozilla/dino-park-front-end
that referenced
this issue
Jun 2, 2021
This was referenced Nov 11, 2021
This was solved in SSO Dashboard ( mozilla-iam/sso-dashboard#447 ) in a parallel effort as I wasn't aware of this work |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Often we hit pull limits in docker which result in failed CodeBuild deployments.
toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit
To Reproduce
Steps to reproduce the behavior:
Execute a codebuild task utilizing Docker.
Expected behavior
No Failure
I've spoken with @sciurus about this and he'd mentioned logging into an account. I'd like to figure out where those credentials are as well as what changes to make to the CodeDeploy build
Also reported in https://mozilla-hub.atlassian.net/browse/IAM-819
The text was updated successfully, but these errors were encountered: