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:
Which area/kind this issue is related to?
/area registry
Issue Description
The scripts contained within the
/build-toolsdirectory in theregistry-supportrepository do not currently supportpodmanaliasing. These scripts are primarily called by CI jobs that can rundocker, however, there is a chance that a developer may need to interact with these scripts locally, and support forpodmanin that case is required.These scripts will need to be altered to adopt changes similar to these by adopting the
setenv.shscript located in the root of theregistry-supportrepository. Changing the scripts in/build-toolscomes 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-toolscan be found below:This filtered search can also be of assistance: https://github.com/search?q=org%3Adevfile+build-tools&type=code&p=1
Acceptance Criteria
/build-toolsdirectory supportpodmanaliasing/build-toolsare able to function with the changes