Hello Ansiblers 
,
I’m looking into setting up a private Ansible Galaxy using Docker, but I see that the latest available image is quay.io/pulp/galaxy:4.9.2, while the latest release of galaxy_ng is 4.10.1.
I assume this is because ansible-hub-ui is still at version 4.9.2.
Do we have a release date for the quay.io/pulp/galaxy:4.10.x image?
Thanks in advance,
SLedunois
See the contents of this PR for information: Add docs for building custom images & current galaxy images policy by gerrod3 · Pull Request #692 · pulp/pulp-oci-images · GitHub
Effectively there are no more galaxy_ng containers being built for new versions.
!!! note "Note on Galaxy images"
We are no longer building any newer image versions of galaxy-ng>=4.10. We will still continue
to build new Z-updates for existing tags, but going forward the `stable` and `latest` tags are
now discontinued.
Ok, thank you very much. Now I understand better!
Does anyone know why there are no new images?
These images were not published or maintained by any ansible/galaxy developers and were never intended for public consumption, although reference to their existence did appear in the galaxy_ng docs at some point. They were published by another team (Pulp) and the way in which they were built and the controls around building them were not stable. They were originally built because they could be built, but not because they were asked to.
Part of the issue related to the fact that the pulp team had no control over what versions of packages appeared in the build, and thus there was no gaurantee that the builds would even be functional or match expected deployments. Those that were functional were basically happenstance, although it appears the vast majority were functional. Failures in builds were also not able to be remedied, and due to the intent of the pipeline that built them, modfications to the build pipelines were not made.
As a result of the overhead and unreliability of the containers, the Pulp team stopped building them.
That makes total sense. Thanks!
I understand the answer, but for me, it’s more tricky than that.
This image officially appears in the Galaxy NG installation documentation (Installation - Galaxy NG). It’s the only solution shown for installing Galaxy NG.
The pulp project and galaxy ng no longer release the images without proposing an alternative solution for installation, which makes the documentation obsolete. I understand why you don’t want to build and manage these images, but no clear documentation is really offered on the Galaxy NG side, and the documentation sent on the pulp project is obscure.
Thanks @SLedunois - we’ve communicated the problem to the galaxy team internally.
The thing is that the image from pulp is having issues and nobody here is replying to the questions (which now I totally understand why). Is there somewhere really well hidden some installation guide for my own Galaxy? Like how do you install it? Or with whom can I discuss my installation roadblocks?
Under the category of ‘I haven’t a clue what I’m talking about’ … is it possible anything under Development - Galaxy NG could help you set this up locally?
Is there ansible_ng container file for custom built?
The galaxy-operator exists and can be used to spin up a local instance of Ansible Galaxy.
It utilizes the quay.io/ansible/galaxy-ng image, however this image does not track Galaxy releases such as 4.9, 4.10, etc. Instead it is built for each commit to the default branch of ansible/galaxy_ng
It seems like galaxy-operator only have dockerfile to build operator itself.