# Galaxy docker image release

**URL:** <https://forum.ansible.com/t/galaxy-docker-image-release/40217>\
**Category:** Get Help\
**Tags:** galaxy-ng\
**Created:** [February 12, 2025, 2:13pm UTC](https://forum.ansible.com/t/galaxy-docker-image-release/40217 "2025-02-12T14:13:23Z")\
**Posts on this page:** 13\
**Page:** 1

<div class="post-metadata">

**Author:** ![SLedunois](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/sledunois/32/7566_2.png) [@SLedunois](https://forum.ansible.com/u/SLedunois)\
**Post date:** [February 12, 2025, 2:13pm UTC](https://forum.ansible.com/t/galaxy-docker-image-release/40217/1 "2025-02-12T14:13:23Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![sivel](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/sivel/32/1198_2.png) [@sivel](https://forum.ansible.com/u/sivel)\
**Post date:** [February 12, 2025, 3:25pm UTC](https://forum.ansible.com/t/galaxy-docker-image-release/40217/2 "2025-02-12T15:25:58Z")

</div>

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](https://github.com/pulp/pulp-oci-images/pull/692)

Effectively there are no more `galaxy_ng` containers being built for new versions.

```auto
!!! 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. 

```

---

<div class="post-metadata">

**Author:** ![SLedunois](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/sledunois/32/7566_2.png) [@SLedunois](https://forum.ansible.com/u/SLedunois)\
**Post date:** [February 12, 2025, 4:16pm UTC](https://forum.ansible.com/t/galaxy-docker-image-release/40217/3 "2025-02-12T16:16:10Z")

</div>

Ok, thank you very much. Now I understand better! 🙂

---

<div class="post-metadata">

**Author:** ![felixfontein](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/felixfontein/32/7530_2.png) [@felixfontein](https://forum.ansible.com/u/felixfontein)\
**Post date:** [February 12, 2025, 5:07pm UTC](https://forum.ansible.com/t/galaxy-docker-image-release/40217/4 "2025-02-12T17:07:49Z")

</div>

Does anyone know _why_ there are no new images?

---

<div class="post-metadata">

**Author:** ![sivel](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/sivel/32/1198_2.png) [@sivel](https://forum.ansible.com/u/sivel)\
**Post date:** [February 12, 2025, 6:19pm UTC](https://forum.ansible.com/t/galaxy-docker-image-release/40217/5 "2025-02-12T18:19:53Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![felixfontein](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/felixfontein/32/7530_2.png) [@felixfontein](https://forum.ansible.com/u/felixfontein)\
**Post date:** [February 12, 2025, 7:08pm UTC](https://forum.ansible.com/t/galaxy-docker-image-release/40217/6 "2025-02-12T19:08:57Z")

</div>

That makes total sense. Thanks!

---

<div class="post-metadata">

**Author:** ![SLedunois](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/sledunois/32/7566_2.png) [@SLedunois](https://forum.ansible.com/u/SLedunois)\
**Post date:** [February 13, 2025, 1:45pm UTC](https://forum.ansible.com/t/galaxy-docker-image-release/40217/7 "2025-02-13T13:45:40Z")

</div>

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](https://ansible.readthedocs.io/projects/galaxy-ng/en/latest/usage_guide/installation/)). 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.

---

<div class="post-metadata">

**Author:** ![samccann](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/samccann/32/18_2.png) [@samccann](https://forum.ansible.com/u/samccann)\
**Post date:** [February 14, 2025, 3:01pm UTC](https://forum.ansible.com/t/galaxy-docker-image-release/40217/8 "2025-02-14T15:01:16Z")

</div>

Thanks @SLedunois - we’ve communicated the problem to the galaxy team internally.

---

<div class="post-metadata">

**Author:** ![Marketa\_Muzikova](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/marketa_muzikova/32/3120_2.png) [@Marketa\_Muzikova](https://forum.ansible.com/u/Marketa_Muzikova)\
**Post date:** [February 26, 2025, 12:14pm UTC](https://forum.ansible.com/t/galaxy-docker-image-release/40217/9 "2025-02-26T12:14:22Z")

</div>

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?

---

<div class="post-metadata">

**Author:** ![samccann](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/samccann/32/18_2.png) [@samccann](https://forum.ansible.com/u/samccann)\
**Post date:** [February 26, 2025, 4:18pm UTC](https://forum.ansible.com/t/galaxy-docker-image-release/40217/10 "2025-02-26T16:18:01Z")

</div>

Under the category of ‘I haven’t a clue what I’m talking about’ … is it possible anything under [Development - Galaxy NG](https://ansible.readthedocs.io/projects/galaxy-ng/en/latest/community/devstack/) could help you set this up locally?

---

<div class="post-metadata">

**Author:** ![AndrewDi](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/andrewdi/32/8090_2.png) [@AndrewDi](https://forum.ansible.com/u/AndrewDi)\
**Post date:** [April 9, 2025, 1:31am UTC](https://forum.ansible.com/t/galaxy-docker-image-release/40217/11 "2025-04-09T01:31:11Z")

</div>

Is there ansible\_ng container file for custom built?

---

<div class="post-metadata">

**Author:** ![drodowic](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/drodowic/32/235_2.png) [@drodowic](https://forum.ansible.com/u/drodowic)\
**Post date:** [April 9, 2025, 12:53pm UTC](https://forum.ansible.com/t/galaxy-docker-image-release/40217/12 "2025-04-09T12:53:00Z")

</div>

The [galaxy-operator](https://github.com/ansible/galaxy-operator) exists and can be used to spin up a local instance of Ansible Galaxy.  
It utilizes the [quay.io/ansible/galaxy-ng](https://quay.io/repository/ansible/galaxy-ng?tab=info) 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](https://github.com/ansible/galaxy_ng)

---

<div class="post-metadata">

**Author:** ![AndrewDi](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/andrewdi/32/8090_2.png) [@AndrewDi](https://forum.ansible.com/u/AndrewDi)\
**Post date:** [April 9, 2025, 3:23pm UTC](https://forum.ansible.com/t/galaxy-docker-image-release/40217/13 "2025-04-09T15:23:16Z")

</div>

It seems like galaxy-operator only have dockerfile to build operator itself.
