Galaxy-NG container registry

Get Help
,
1

Hello,

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

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 that could help. I have just added this:

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

but it doesn’t help.

My compose file for Galaxy-NG is

  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

2

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

3

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:

# 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

4

Why don’t you follow the official installation method?

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