# Tags in execution environment images

**URL:** <https://forum.ansible.com/t/tags-in-execution-environment-images/4615>\
**Category:** Get Help\
**Tags:** podman, awx, ansible-builder, ee\
**Created:** [March 28, 2024, 2:20pm UTC](https://forum.ansible.com/t/tags-in-execution-environment-images/4615 "2024-03-28T14:20:55Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![jpmens](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/jpmens/32/5543_2.png) [@jpmens](https://forum.ansible.com/u/jpmens)\
**Post date:** [March 28, 2024, 2:20pm UTC](https://forum.ansible.com/t/tags-in-execution-environment-images/4615/1 "2024-03-28T14:20:55Z")

</div>

This might well be a wee bit off-topic for this forum, but as I’m building awx execution environment images, I’m hoping somebody can help me.

I build an EE image with multiple tags like this:

```console
$ ansible-builder build --squash all --tag REPO/wheel:latest --tag REPO/wheel:1.7
$ podman push REPO/wheel:latest

```

and push the image to a package repository hosted on a local Forgejo (gitea) installation. When looking at the list of packages, I see a version `:latest`.

What I’d actually like to see is a version `1.7`, say, which can also be pulled with the tag `:latest`, but the only way I seem to be able to accomplish this is with two distinct `podman push`, one for `:1.7` and the other for `:latest`.

Is this normal or am I using `ansible-builder` incorrectly?

```auto
ansible-builder: 3.0.1
podman: 4.3.1
debian: 12
forgejo: 1.21.8

```

---

<div class="post-metadata">

**Author:** ![kurokobo](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/kurokobo/32/182_2.png) [@kurokobo](https://forum.ansible.com/u/kurokobo)\
**Post date:** [March 28, 2024, 3:01pm UTC](https://forum.ansible.com/t/tags-in-execution-environment-images/4615/2 "2024-03-28T15:01:18Z")

</div>

> the only way I seem to be able to accomplish this is with two distinct `podman push` , one for `:1.7` and the other for `:latest` .

AFAIK, this is intended. You shoukd invoke `podman push` twice.

`docker push` has an option `--all-tags` that can push all tags of the same image (`docker push REPO/wheel --all-tags`), but `podman push` does not have this option.

It appears that an implementation of the same option has been proposed for Podman in the past, but has been passed over to avoid a situation where unintended images are pushed together. Indeed, the `--all-tags` option can be a bit overkill because it pushes all tags anyway, even if the IMAGE IDs are different.

- [podman push --all-tags · Issue #2369 · containers/podman · GitHub](https://github.com/containers/podman/issues/2369)
- [Add --all-tags to push by TomSweeneyRedHat · Pull Request #1380 · containers/buildah · GitHub](https://github.com/containers/buildah/pull/1380#pullrequestreview-210936302)

---

<div class="post-metadata">

**Author:** ![jpmens](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/jpmens/32/5543_2.png) [@jpmens](https://forum.ansible.com/u/jpmens)\
**Post date:** [March 28, 2024, 3:06pm UTC](https://forum.ansible.com/t/tags-in-execution-environment-images/4615/3 "2024-03-28T15:06:03Z")

</div>

Thank you, @kurokobo

I think I’ll then just push the numbered tag (`:1.7`). It _seems_ sensible to me at this point to force AWX users to think about the EE version they want to run and not let them just say `:latest`.

(Opinions gladly heard! 🙂 )

---

<div class="post-metadata">

**Author:** ![kurokobo](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/kurokobo/32/182_2.png) [@kurokobo](https://forum.ansible.com/u/kurokobo)\
**Post date:** [March 28, 2024, 3:31pm UTC](https://forum.ansible.com/t/tags-in-execution-environment-images/4615/4 "2024-03-28T15:31:43Z")

</div>

Agree with you, I too think `latest` should not be used much. The `latest` will cause trouble in the long term.

The users won’t notice if the `latest` is updated, and if a job fails because of updated `latest`, any way to use the old image again never be provided to users. Not only that, if the cached `latest` image differs from node to node, it is possible for a job to fail only when it is launched on a particular node.

Similar discussion is here: [Bind EE images version with DEFAULT\_AWX\_VERSION by bartowl · Pull Request #1740 · ansible/awx-operator · GitHub](https://github.com/ansible/awx-operator/pull/1740#discussion_r1517162486)

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/ansible/original/1X/1882d9a01da5d8996a862359b0913cc568a39b84.svg) [@system](https://forum.ansible.com/u/system)\
**Post date:** [April 27, 2024, 3:32pm UTC](https://forum.ansible.com/t/tags-in-execution-environment-images/4615/5 "2024-04-27T15:32:33Z")

</div>

Closed on April 27, 2024, 3:32pm UTC

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.