There was a new version of the APB published 6 days ago to the {{latest}} tag. This includes ansible 2.7.0:
{noformat}
$ docker run --rm -ti --entrypoint ansible aerogearcatalog/keycloak-apb:latest --version
ansible 2.7.0
config file = /opt/apb/.ansible.cfg
configured module search path = [u'/opt/apb/.ansible/plugins/modules', u'/usr/share/ansible/plugins/modules']
ansible python module location = /usr/lib/python2.7/site-packages/ansible
executable location = /usr/bin/ansible
python version = 2.7.5 (default, Apr 11 2018, 07:36:10) [GCC 4.8.5 20150623 (Red Hat 4.8.5-28)]
{noformat}
In contrast, the {{1.0.0}} tag of the image uses ansible 2.5.5:
{noformat}
$ docker run --rm -ti --entrypoint ansible aerogearcatalog/keycloak-apb:1.0.0 --version
ansible 2.5.5
config file = /opt/apb/ansible.cfg
configured module search path = [u'/opt/apb/.ansible/plugins/modules', u'/usr/share/ansible/plugins/modules']
ansible python module location = /usr/lib/python2.7/site-packages/ansible
executable location = /usr/bin/ansible
python version = 2.7.5 (default, Aug 4 2017, 00:39:18) [GCC 4.8.5 20150623 (Red Hat 4.8.5-16)]
{noformat}
I'm not sure if that's a possible reason for the issues that you're seeing, or even if it's the {{latest}} or {{1.0.0}} image that you're using. There could be other changes in the base image causing this issue (or even in our image). |
|
