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

publish images to quay.io too #1995

Closed
6543 opened this issue Jul 13, 2023 · 5 comments
Closed

publish images to quay.io too #1995

6543 opened this issue Jul 13, 2023 · 5 comments
Assignees
Labels
build CI pipeline related

Comments

@6543
Copy link
Member

6543 commented Jul 13, 2023

next to docker.io push to quay.io too

@anbraten
Copy link
Member

anbraten commented Jul 14, 2023

I wouldn't add quay.io at the moment. Docker-hub is free for us again and currently works. With the recent things going on at RedHat I am not really sure if quay.io is a better place. Adding any additional registry would currently just be maintenance overhead and adds additional problems.

@xoxys
Copy link
Member

xoxys commented Jul 26, 2023

What problems do you see that would be added? IMO, relying on the availability of a single public registry is a bad idea and has already caused trouble for many users in the past. Removing DockerHub in favor of Quay may be questionable, but I would like to see at least a second registry added as fallback. This could be Quay or GitHub Container registry. The maintenance overhead is also quite low to my experiences. I have set this up for a lot of repos and it "just works" reliable in the same way it works for the DockerHub upload process of your CI.

@anbraten
Copy link
Member

anbraten commented Jul 27, 2023

As long as all works its most of the time fine, until sth does not work straightforward. All those tiny things are often adding maintenance overhead in the end. Things like uploading does not work (credentials are outdated, ...), we need to update all image strings at all places in code, docs etc, users could be confused which registry to choose, ...

In general saying no for now is hard, but in the long term its way easier to say yes and to add complexity / change registry, ... than removing and migrating the whole community again.

@6543 6543 self-assigned this Jul 27, 2023
@xoxys
Copy link
Member

xoxys commented Jul 27, 2023

I see. In case Docker will decide tomorrow to kill all open source free projects (and we had nearly such situations already) things will become unusable immediately. That's all I wanted to add.

@6543
Copy link
Member Author

6543 commented Jul 27, 2023

I'll add and maintain that :)

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

No branches or pull requests

3 participants