when running the ./manual-publish.sh script if you have a local copy of the tssc-base image tagged with the upstream tag that the manually built images are dependent on, then podman build uses that cached image tag rather then pulling latest from remote repo.
when merging and then publishing the manual images for https://github.com/rhtconsulting/tssc-containers/pull/26 this meant that the buildah image ended up using a locally cached version of tssc-base which didn't have the required changes and then caused failures during integration testing.
resolution
set the --pull-always flag on the podman build command to be sure that the remote images are always pulled even if there is a local image.
jkeam
commented
3 years ago
issue
when running the
./manual-publish.shscript if you have a local copy of the tssc-base image tagged with the upstream tag that the manually built images are dependent on, thenpodman builduses that cached image tag rather then pulling latest from remote repo.when merging and then publishing the manual images for https://github.com/rhtconsulting/tssc-containers/pull/26 this meant that the buildah image ended up using a locally cached version of tssc-base which didn't have the required changes and then caused failures during integration testing.
resolution
set the
--pull-alwaysflag on thepodman buildcommand to be sure that the remote images are always pulled even if there is a local image.