Skip to content
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

The nightly plugins tests are failed on the openshift CI because reached the docker pull limit #20700

Closed
Ohrimenko1988 opened this issue Oct 28, 2021 · 1 comment
Assignees
Labels
kind/task Internal things, technical debt, and to-do tasks to be performed. sprint/current status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github.

Comments

@Ohrimenko1988
Copy link
Contributor

Is your task related to a problem? Please describe

The nightly plugins tests are failed on the openshift CI because reached the docker pull limit

error: build error: failed to pull image: After retrying 2 times, Pull image still failed due to error: Error initializing source docker://node:14.17.6-alpine3.12: Error reading manifest 14.17.6-alpine3.12 in docker.io/library/node: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit
�[36mINFO�[0m[2021-10-28T00:07:13Z] Ran for 6m4s                                 
�[31mERRO�[0m[2021-10-28T00:07:13Z] Some steps failed:                           
�[31mERRO�[0m[2021-10-28T00:07:13Z] 
  * could not run steps: step che-plugin-registry failed: the build che-plugin-registry failed after 2m29s with reason PullBuilderImageFailed: Failed pulling builder image. 

Describe the solution you'd like

Mirror the docker.io/node:14.17.6-alpine3.12 image to quay.io registry and use mirrored image in the tests Dockerfile

Describe alternatives you've considered

No response

Additional context

No response

@Ohrimenko1988 Ohrimenko1988 added the kind/task Internal things, technical debt, and to-do tasks to be performed. label Oct 28, 2021
@che-bot che-bot added the status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. label Oct 28, 2021
@Ohrimenko1988 Ohrimenko1988 self-assigned this Oct 28, 2021
@svor svor mentioned this issue Oct 28, 2021
28 tasks
@Ohrimenko1988
Copy link
Contributor Author

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/task Internal things, technical debt, and to-do tasks to be performed. sprint/current status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github.
Projects
None yet
Development

No branches or pull requests

3 participants