Podman Support For Registry Support Build Tools

[Jdubrick]

Which area/kind this issue is related to?

/area registry

Issue Description

The scripts contained within the /build-tools directory in the registry-support repository do not currently support podman aliasing. These scripts are primarily called by CI jobs that can run docker, however, there is a chance that a developer may need to interact with these scripts locally, and support for podman in that case is required.

These scripts will need to be altered to adopt changes similar to these by adopting the setenv.sh script located in the root of the registry-support repository. Changing the scripts in /build-tools comes with the added overhead of ensuring that all CI jobs calling these scripts as well as other scripts in other project repositories are able to function the same with the changes.

An example of CI jobs calling scripts within /build-tools can be found below:

• https://github.com/devfile/registry/blob/66088eef948ade542ddf4957ffb450aaa3136f36/.ci/Dockerfile#L29
• https://github.com/devfile/registry/blob/66088eef948ade542ddf4957ffb450aaa3136f36/.ci/Dockerfile.offline#L29
• https://github.com/devfile/registry-support/blob/954a12f6748de77af96a6c1ffdbcc0e8a690e072/.ci/Dockerfile#L25
• https://github.com/devfile/registry/blob/66088eef948ade542ddf4957ffb450aaa3136f36/.github/workflows/pushimge-next.yaml#L51

This filtered search can also be of assistance: https://github.com/search?q=org%3Adevfile+build-tools&type=code&p=1

Acceptance Criteria

• Scripts contained within /build-tools directory support podman aliasing
• CI jobs and scripts invoking scripts from /build-tools are able to function with the changes

[github-actions]

This issue is stale because it has been open for 90 days with no activity. Remove stale label or comment or this will be closed in 60 days.