# Galaxy-NG container registry

**URL:** <https://forum.ansible.com/t/galaxy-ng-container-registry/9635>\
**Category:** Get Help\
**Tags:** galaxy-ng, ee\
**Created:** [October 2, 2024, 11:18am UTC](https://forum.ansible.com/t/galaxy-ng-container-registry/9635 "2024-10-02T11:18:34Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![falon](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/falon/32/2081_2.png) [@falon](https://forum.ansible.com/u/falon)\
**Post date:** [October 2, 2024, 11:18am UTC](https://forum.ansible.com/t/galaxy-ng-container-registry/9635/1 "2024-10-02T11:18:34Z")

</div>

Hello,

I have installed a **Galaxy-NG** server and I have read in EE section that it provides a local podman registry:

> **[Execution Environments - Galaxy NG](https://ansible.readthedocs.io/projects/galaxy-ng/en/latest/usage_guide/execution_environments/)**
>
> Galaxy NG

> Galaxy NG provides a container registry for pushing container images. It functions just like any other container registry and can be accessed with all the standardized container tools.

Really, I can’t find in documentation how to enable this container registry. If I access the Galaxy-NG container, I can’t see the registry and the port 5001 is not listening.

I don’t recognize [config options](https://ansible.readthedocs.io/projects/galaxy-ng/en/latest/config/options/) that could help. I have just added this:

```auto
GALAXY_FEATURE_FLAGS = {
  "dynaconf_merge": True,
  "execution_environments": True
}

```

but it doesn’t help.

My compose file for Galaxy-NG is

```yaml
  Galaxy-NG:
    ports:
      - 80:80
      - 5001:5001
    container_name: Galaxy-NG
    volumes:
      - /opt/config/galaxy_ng/settings:/etc/pulp:Z
      - /opt/data/galaxy_ng/pulp_storage:/var/lib/pulp:Z
      - /opt/data/galaxy_ng/pgsql:/var/lib/pgsql:Z
      - /opt/data/galaxy_ng/containers:/var/lib/containers:Z
    devices:
      - /dev/fuse
    image: quay.io/pulp/galaxy:4.9.2

```

Could you help me?  
Thank you very much  
Kind Regards  
Marco

---

<div class="post-metadata">

**Author:** ![kurokobo](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/kurokobo/32/182_2.png) [@kurokobo](https://forum.ansible.com/u/kurokobo)\
**Post date:** [October 2, 2024, 1:15pm UTC](https://forum.ansible.com/t/galaxy-ng-container-registry/9635/2 "2024-10-02T13:15:32Z")

</div>

Hi, in the first place how did you install Galaxy NG?

---

<div class="post-metadata">

**Author:** ![falon](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/falon/32/2081_2.png) [@falon](https://forum.ansible.com/u/falon)\
**Post date:** [October 2, 2024, 2:56pm UTC](https://forum.ansible.com/t/galaxy-ng-container-registry/9635/3 "2024-10-02T14:56:48Z")

</div>

Hello,

I installed Galaxy-NG using **podman-compose** with the above compose file, using the image `quay.io/pulp/galaxy:4.9.2`.

I wrote these settings in **settings.py** :

```auto
# cat /opt/config/galaxy_ng/settings/settings.py
CONTENT_ORIGIN='http://galaxy.example.com'
ANSIBLE_API_HOSTNAME='http://galaxy.example.com'
ANSIBLE_CONTENT_HOSTNAME='http://galaxy.example.com/pulp/content'
GALAXY_REQUIRE_CONTENT_APPROVAL=False
GALAXY_FEATURE_FLAGS = {
  "dynaconf_merge": True,
  "execution_environments": True
}

```

Thank you  
Marco

---

<div class="post-metadata">

**Author:** ![kurokobo](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/kurokobo/32/182_2.png) [@kurokobo](https://forum.ansible.com/u/kurokobo)\
**Post date:** [October 2, 2024, 3:02pm UTC](https://forum.ansible.com/t/galaxy-ng-container-registry/9635/4 "2024-10-02T15:02:00Z")

</div>

Why don’t you follow the official installation method?

> **[Installation - Galaxy NG](https://ansible.readthedocs.io/projects/galaxy-ng/en/latest/usage_guide/installation/)**
>
> Galaxy NG

Example configuration files are provided and you can see the line `PULP_GALAXY_FEATURE_FLAGS__execution_environments` in that file.