Unable to find a pulp/galaxy source repo to build it on ppc64le

[prabhuk25]

Hello Team,
I want to build the pulp/galaxy image(quay.io/pulp/galaxy) on ppc64le to build and test ansible package(https://github.com/ansible/ansible).
However, I am not finding a source repo for this image and as I checked, somewhere i found that it is EOL, so how do I proceed further for building an ansible package. Will there be any alternative approach.
It would be very helpful if you suggest best approach to procced further.

[gerrod3]

@prabhuk25 Yes the pulp/galaxy image is no longer supported so you have two options:

1. Use the normal Pulp image which includes pulp_ansible to upload your collections to: https://pulpproject.org/pulp_ansible/docs/user/guides/collections/
2. Use Ansible's GalaxyNG image for your testing. https://github.com/ansible/galaxy_ng/. This is what https://galaxy.ansible.com uses as its backend. They have Dockerfiles and instructions on how to set up a galaxy instance

[prabhuk25]

Thanks for the response @gerrod3!
I had tried with ansible/galaxy_ng image on x86, since it has support of x86; if it works will plan to build on ppc64le, but it's not working as expected; it's failing with Permssion issue. Ideally, it should work without any tweaks for the image.
Also, I can see a couple of warnings about Volume leakage
You can see the same below:
`WARNING: Image "quay.io/pulp/galaxy:4.7.1" contains 3 volume(s): /etc/pulp, /tmp/ansible, /var/lib/pulp
This may result in leaking anonymous volumes. It may also prevent the image from working on some hosts or container engines.
The image should be rebuilt without the use of the VOLUME instruction.
Adding "galaxy-pulp-6T7fGdC8" to container database.
FATAL: Command "docker exec 3****2 mkdir -p /etc/galaxy-importer" returned exit status 1.

Standard Error
mkdir: cannot create directory ‘/etc/galaxy-importer’: Permission denied`

And for 1st approach, seems it won't work, since while running integration test, over the run time it automatically pulls images and starts container and so on, so it's difficult to follow this approach, it would be helpful if you provide more info about the same.

[gerrod3]

@prabhuk25 Did you run the ansible galaxy_ng image? They don't publish it, you have to build it with docker compose: https://docs.ansible.com/projects/galaxy-ng/en/latest/usage_guide/installation.html. The pulp/galaxy image is no longer supported and uses an outdated version of galaxy.

Also, for your second point I don't understand what you mean about integration tests pulling images. Is there something specific you need your Pulp to do besides storing pushed collections?

[prabhuk25]

@gerrod3, Just to clarify: as I mentioned earlier, I was running an integration test on ansible-repo, and the repo has a dependency on pulp/galaxy and other images, so on the fly it will pull the image and execute a container, so we can't go with the below approach manually:
1. Use the normal Pulp image which includes pulp_ansible to upload your collections to: https://pulpproject.org/pulp_ansible/docs/user/guides/collections/

And yeah, I had built an image and executed a test, but it was still failing with an execute permission issue as mentioned earlier.

[gerrod3]

@prabhuk25 Hmm, I didn't know they hadn't swapped over in the main ansible repo. Tragic. Well the next best option is to take the last image branch and see if you can build it: https://github.com/pulp/pulp-oci-images/tree/3.49/images/galaxy. We haven't touched it in two years so no idea if it will build