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

fix(quay.io): start using quay.io and fix backup push #805

Merged
merged 11 commits into from
Mar 12, 2023
Merged

Conversation

brokenpip3
Copy link
Collaborator

Submitter Checklist

These are the criteria that every PR should meet, please check them off as you
review them:

See the contribution guide for more details.

Release Notes

Start using quay.io and fix backup build/push

@brokenpip3 brokenpip3 merged commit 2f90db9 into master Mar 12, 2023
@brokenpip3 brokenpip3 deleted the quayio_fixies branch March 12, 2023 17:29
@tomvopat
Copy link

tomvopat commented Apr 5, 2023

@brokenpip3, why is it better to move from Docker Hub to quay.io? Is it personal preference or is there some other reason?

@brokenpip3
Copy link
Collaborator Author

nothing personal obv :)

We need to move from the virtuslab docker org and since in docker you have rate limit by default and that could hit our users and in quay.io you do not have the same issue we agreed with virtuslab maintainers of using quay.io.
Another option could be the github registry but since in the last month we are using quay.io and it's working great I do not see any cons with it.
There is something you are aware that we do not considered?

@tomvopat
Copy link

tomvopat commented Apr 5, 2023

Thanks for explanation! I just wasn't aware of this limitation, so I asked...

@brokenpip3
Copy link
Collaborator Author

make sense :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants