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

[Testing] tests flaky when pulling from dockerhub #5425

Closed
Bobgy opened this issue Apr 3, 2021 · 7 comments
Closed

[Testing] tests flaky when pulling from dockerhub #5425

Bobgy opened this issue Apr 3, 2021 · 7 comments
Labels
lifecycle/stale The issue / pull request is stale, any activities remove this label.

Comments

@Bobgy
Copy link
Contributor

Bobgy commented Apr 3, 2021

See https://oss-prow.knative.dev/view/gs/oss-prow/pr-logs/pull/kubeflow_pipelines/5424/kubeflow-pipeline-e2e-test/1378351440040300544#1:build-log.txt%3A1308

Step #1 - "scheduledworkflow": Get https://registry-1.docker.io/v2/: net/http: request canceled (Client.Timeout exceeded while awaiting headers)

The same error message happens randomly during different image build process.

@Bobgy
Copy link
Contributor Author

Bobgy commented Apr 3, 2021

From PR #5424

@NikeNano
Copy link
Member

NikeNano commented Apr 3, 2021

Do you know what this error comes from? These images should be on google container registry as I understand, are there any rate limiting?

@Bobgy
Copy link
Contributor Author

Bobgy commented Apr 3, 2021

Let me elaborate, the above error occurs when we are building KFP docker images, we need to pull some common images from dockerhub as the base.

@NikeNano
Copy link
Member

NikeNano commented Apr 4, 2021

Ok, thanks! Do you expect these errors to be due to the rate limit? Could we move the base images to gcr as well?

@Bobgy
Copy link
Contributor Author

Bobgy commented Apr 4, 2021

I agree. Looks like it recovered, if it keeps happening, we should do that

@stale
Copy link

stale bot commented Jul 8, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the lifecycle/stale The issue / pull request is stale, any activities remove this label. label Jul 8, 2021
@stale
Copy link

stale bot commented Apr 18, 2022

This issue has been automatically closed because it has not had recent activity. Please comment "/reopen" to reopen it.

@stale stale bot closed this as completed Apr 18, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/stale The issue / pull request is stale, any activities remove this label.
Projects
None yet
Development

No branches or pull requests

2 participants