Closed douglas closed 1 year ago
@newswangerd, @decko, @fao89 and @jctanner: if I would take a stab at https://github.com/pulp/pulp-oci-images/pull/369, how can I see the failures on pulp-operator ci? Are there like a staging environment y'all use to build all these images?
I suppose I can't just rely on Github checks since you had to merge it first, right @fao89?
@newswangerd, @decko, @fao89 and @jctanner: if I would take a stab at pulp/pulp-oci-images#369, how can I see the failures on pulp-operator ci? Are there like a staging environment y'all use to build all these images?
I suppose I can't just rely on Github checks since you had to merge it first, right @fao89?
you can build your images, point them here: https://github.com/pulp/pulp-operator/blob/main/config/samples/galaxy.yaml#L7-L10 start a PR and check the CI logs here https://github.com/pulp/pulp-operator/actions/runs/5239103318/jobs/9466546710
What are you trying to achieve?
Add troubleshooting tips to help other developers trying to setup
pulp
and related projects in macOS runningarm64
chips.Context about the changes
When I was trying to setup this project on my
arm64
machine, I noticed no matter what I tried, the setup didn't work as smoothly as it did in myPop!_OS
machine, so I got super curious to understand where was the problem.After some debugging and archaeology, I think I understood the reason why it was failing and found a way to have it working locally so I decided to document the process to help other fellow developers to try it out on their macOS machines =)