Also, once we do this, I’d like to consider changing the default EE image that ansible-navigator uses from the gigantic creator-ee image to this one. It’s not a good user experience when the software starts downloading a 500MB+ image without user input before you can even use it.
1 Like
A couple of updates on the topic:
- The new galaxy.ansible.com based on galaxy-ng will have the execution environments (ee) feature available in the code base and there is an ongoing discussion on when and how to enable it, so in the future we might be able to migrate to it
- Apparently we are duplicating
creator-eein both, quay.io and ghcr. My main concern for ghcr is that, afaik, it’s tied to GitHub as a platform.
GHCR is tied to Github, Quay is tied to the Red Hat’s business interests, and Docker Hub is… I don’t want to block this on anything, but it seems Galaxy NG’s registry is ultimately the best place for this.
1 Like
Yes, I would advocate that RH is the main sponsor of Ansible itself, and Quay is supposed to be more “interoperable” though. But I do think that GHCR looks like the “easier and faster” way.
To clarify: Galaxy NG is not an option right now, hopefully it will be soon, but until that is enabled, the choice remains between Quay.io and GHCR for now.
The vote has been open for 28 days, we should probably close it and get working on the outcome 
1 Like
Not to derail finalizing this, but is this something the Steering Committee should decide? (in which case we need an SC poll here).
1 Like
@anwesha you might want to close that poll eventually. It makes this thread show up under “Open Polls” in the sidebar menu, which could be confusing since I don’t think anyone still looks at the results of this poll.
1 Like
I closed it, thanks @felixfontein
1 Like