Request: Immutable tags on docker hub about docker-ansible HOT 9 CLOSED

I have been affected by this too, it broke CI workflow.

Looks to me that this commit is the culprit
32998c7

@willhallonline as this removed packages from the Docker image, it a breaking change on the same image tag. I think the change should be reverted. Many workflows might be affected.

from docker-ansible.

Same for our project. Without notice our Gitlab CI broke.

from docker-ansible.

Maybe try using devture/ansible . It's based on Alpine Linux though, so depending on your setup, you might have to adjust your CI/CD-Scripts. Also, it's on Ansible 2.9, but at least it has immutable tags.

from docker-ansible.

I am sorry about this. At the moment, I am not doing immutable tags, mainly because of the burden of managing multiple OS/Ansible combinations (about 33 at the moment) and increasing that would just take more work. I do intend to move the Ansible version install to be a variable though which would resolve some of these problems (or at least make it easier to build and own).

from docker-ansible.

@InterFelix, @goetzc, @thaarhoff : what versions would you like as immutable? I want to keep rebuilding the containers on a stable base image, however, have now implemented that I could release different Ansible versions as required? Or is it rather that you would like to maintain every version of Ansible?

from docker-ansible.

What I was initially thinking was "just add a tag with the minor version on release", so when an image gets built with Ansible 2.10.12 for example you can directly refer to it by its version. Now it basically gets overwritten by a new minor update of Ansible 2.10 without any way of referring back to the image that contained 2.10.12 as the minor version.

The underlying problem is that a minor update broke compatibility in my case, which shouldn't ever happen, but it did, but that's Ansible's fault, not yours.

from docker-ansible.

I could probably now relatively easily do that (easier than it was before my new changes)... So rather than willhallonline/ansible:2.10-alpine-3.15 it becomes willhallonline/ansible:2.10.12-alpine-3.15?

Maybe I also keep willhallonline/ansible:2.10-alpine-3.15 which is rebuilt at newest all the time, but the old ones stay fixed (including older packages inside Alpine-3.15)?

from docker-ansible.

That's exactly what I had in mind. Just put a tag that explicitly identifies the minor version on each image so there's a way to target a specific minor version.

from docker-ansible.

This is completed now . I have created immutable tags within all OS from the latest Ansible version inside:

• 2.9.27-[All]
• 2.10.17-[All]
• 2.11.8 - [All]
• 2.12.2 - Excluding Some.

Inside tag v4.0.1.

from docker-ansible.