[Podman] Re: Pushing image tagged with multiple tags to remote repo with the same digest

I would only like to mention that buildah 1.18.0 was on my local system, but on CI I was using the latest version from https://quay.io/repository/buildah/stable (as of 17 Feb) and the problem was still there.

buildah version 1.19.6 (image-spec 1.0.1-dev, runtime-spec 1.0.2-dev)

On 2021-02-17 20:08, Daniel Walsh wrote: > Miloslav and Nalin could one of you answer the question? > > On 2/17/21 12:08, Marcin Zajączkowski wrote: >> Hi. I might miss something obvious - I don't have deep knowledge about >> containers, however, trying to migrate my docker-in-docker image >> building CI job to buildah, I've encountered the following problem. >> >> My image should be tagged with its real version and in addition with a >> special marker tag (such as "devel" or "stable" or "latest"). It seems >> to be a common practice with images. While in docker, I could just call: >>> docker build -t "$CI_REGISTRY_IMAGE:$VERSION" -t >>> "$CI_REGISTRY_IMAGE:$MARKER_TAG" >>> docker push $CI_REGISTRY_IMAGE" >> with buildah, it is more problematic as I cannot use multiple tags on >> push (--all-tags switch has been also abandoned). >> >> I tried: >>> buildah bud -t "$CI_REGISTRY_IMAGE:$VERSION" -t >>> "$CI_REGISTRY_IMAGE:$MARKET_TAG" >>> buildah push "$CI_REGISTRY_IMAGE:$VERSION" "$CI_REGISTRY_IMAGE:$VERSION" >>> buildah push "$CI_REGISTRY_IMAGE:$MARKET_TAG" >>> "$CI_REGISTRY_IMAGE:$MARKET_TAG" >> but while "buildah images --digests" shows the same digest for those two >> tags, in the remote repository (GitLab CI container repository) these >> tags have two different digests (also both differ from the local one). I >> suspect there could be something changed in the manifest. >> >> >> Q. How can I have one image (with one digests) tagged multiple times in >> a container repository using buildah? >> >> >> buildah version 1.18.0 (image-spec 1.0.1-dev, runtime-spec 1.0.2-dev) on >> Fedora 33. >> >> Marcin >> >> P.S. I've seen https://github.com/containers/buildah/issues/2034, but I >> don't know if it is related.